Search Options

Display Count
Sort
Preferred Language
Advanced Search

Results 1 - 10 of 37 for _team_ (0.04 seconds)

  1. tests/associations_has_many_test.go

    	if err := DB.Model(&user2).Association("Team").Append(&teams); err != nil {
    		t.Fatalf("Error happened when append team, got %v", err)
    	}
    
    	for _, team := range teams {
    		team := team
    		if team.ID == 0 {
    			t.Fatalf("Team's ID should be created")
    		}
    
    		user.Team = append(user.Team, team)
    	}
    
    	CheckUser(t, user2, user)
    
    Created: Sun Dec 28 09:35:17 GMT 2025
    - Last Modified: Fri Sep 12 04:33:27 GMT 2025
    - 16.3K bytes
    - Click Count (0)
  2. .github/workflows/team-triage-stale.yml

    name: 'Requeue stale team-triage items'
    on:
      schedule:
        # Execute every day at 00:05 to avoid conflicts with other workflows
        - cron: '5 0 * * *'
    
    permissions: {}
    
    jobs:
      requeue:
        permissions:
          issues: write
          pull-requests: write
        runs-on: ubuntu-latest
        steps:
          - uses: actions/stale@v10
            with:
              operations-per-run: 50
              remove-stale-when-updated: false
    
    Created: Wed Dec 31 11:36:14 GMT 2025
    - Last Modified: Thu Sep 04 22:13:29 GMT 2025
    - 836 bytes
    - Click Count (0)
  3. architecture/standards/0001-use-architectural-decision-records.md

    ADRs can be written by any team.
    Like code, they should be reviewed by any other relevant teams.
    The goal is not to *own* a decision, but to *share* it with other teams, and improve the build tool together.
    
    ### Format
    
    The format for ADR should follow this template:
    
    ```markdown
    # ADR-000X - Title
    
    ## Date
    
    20YY-MM-DD
    
    ## Context
    
    Created: Wed Dec 31 11:36:14 GMT 2025
    - Last Modified: Tue Aug 26 17:29:22 GMT 2025
    - 2.8K bytes
    - Click Count (0)
  4. docs/en/docs/history-design-future.md

    It is being chosen over previous alternatives for suiting many use cases better.
    
    Many developers and teams already depend on **FastAPI** for their projects (including me and my team).
    
    But still, there are many improvements and features to come.
    
    **FastAPI** has a great future ahead.
    
    Created: Sun Dec 28 07:19:09 GMT 2025
    - Last Modified: Sat Oct 11 17:48:49 GMT 2025
    - 4.2K bytes
    - Click Count (0)
  5. docs/de/docs/history-design-future.md

    Es wird gegenüber früheren Alternativen gewählt, da es für viele Anwendungsfälle besser geeignet ist.
    
    Viele Entwickler und Teams verlassen sich bei ihren Projekten bereits auf **FastAPI** (einschließlich mir und meinem Team).
    
    Dennoch stehen uns noch viele Verbesserungen und Funktionen bevor.
    
    **FastAPI** hat eine große Zukunft vor sich.
    
    Created: Sun Dec 28 07:19:09 GMT 2025
    - Last Modified: Sat Oct 11 17:48:49 GMT 2025
    - 4.9K bytes
    - Click Count (0)
  6. .github/CODEOWNERS

    platforms/core-execution/build-cache-http/                  @gradle/bt-cortex @gradle/dv-integrations-team
    platforms/core-execution/build-cache-packaging/             @gradle/bt-cortex @gradle/dv-integrations-team
    platforms/core-execution/build-cache-spi/                   @gradle/bt-cortex @gradle/dv-integrations-team
    platforms/core-execution/hashing/                           @gradle/bt-cortex @gradle/dv-integrations-team
    Created: Wed Dec 31 11:36:14 GMT 2025
    - Last Modified: Fri Nov 07 21:47:29 GMT 2025
    - 11K bytes
    - Click Count (0)
  7. docs/en/docs/management-tasks.md

    These are the tasks that can be performed to manage the FastAPI repository by [team members](./fastapi-people.md#team){.internal-link target=_blank}.
    
    /// tip
    
    This section is useful only to a handful of people, team members with permissions to manage the repository. You can probably skip it. 😉
    
    ///
    
    ...so, you are a [team member of FastAPI](./fastapi-people.md#team){.internal-link target=_blank}? Wow, you are so cool! 😎
    
    Created: Sun Dec 28 07:19:09 GMT 2025
    - Last Modified: Wed Dec 17 20:41:43 GMT 2025
    - 14.2K bytes
    - Click Count (0)
  8. docs/de/docs/how-to/migrate-from-pydantic-v1-to-pydantic-v2.md

    FastAPI 0.126.0 entfernte die Unterstützung für Pydantic v1, während `pydantic.v1` noch eine Weile unterstützt wurde.
    
    /// warning | Achtung
    
    Das Pydantic-Team hat die Unterstützung für Pydantic v1 in den neuesten Python-Versionen eingestellt, beginnend mit **Python 3.14**.
    
    Dies schließt `pydantic.v1` ein, das unter Python 3.14 und höher nicht mehr unterstützt wird.
    
    Created: Sun Dec 28 07:19:09 GMT 2025
    - Last Modified: Wed Dec 24 10:28:19 GMT 2025
    - 6.3K bytes
    - Click Count (0)
  9. docs/de/docs/deployment/cloud.md

    ## FastAPI Cloud { #fastapi-cloud }
    
    **<a href="https://fastapicloud.com" class="external-link" target="_blank">FastAPI Cloud</a>** wurde vom selben Autor und Team hinter **FastAPI** entwickelt.
    
    Es vereinfacht den Prozess des **Erstellens**, **Deployens** und **Zugreifens** auf eine API mit minimalem Aufwand.
    
    Created: Sun Dec 28 07:19:09 GMT 2025
    - Last Modified: Tue Dec 02 17:32:56 GMT 2025
    - 1.4K bytes
    - Click Count (0)
  10. docs/en/docs/how-to/migrate-from-pydantic-v1-to-pydantic-v2.md

    FastAPI 0.126.0 dropped support for Pydantic v1, while still supporting `pydantic.v1` for a little while.
    
    /// warning
    
    The Pydantic team stopped support for Pydantic v1 for the latest versions of Python, starting with **Python 3.14**.
    
    This includes `pydantic.v1`, which is no longer supported in Python 3.14 and above.
    
    Created: Sun Dec 28 07:19:09 GMT 2025
    - Last Modified: Sat Dec 20 15:55:38 GMT 2025
    - 5.5K bytes
    - Click Count (0)
Back to Top