- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 3,523 for use (0.15 sec)
-
architecture/standards/0001-use-architectural-decision-records.md
# ADR-0001 - Use Architectural Decision Records ## Date 2023-12-01 ## Context In a distributed team with many subteams, the best solution to communicate decisions is to use a format accessible by everyone in charge of development. We use *Specification* and *Discovery* documents stored in Google Drive, but they present some downsides:
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sat Mar 02 21:54:40 GMT 2024 - 2.8K bytes - Viewed (0) -
architecture/standards/0004-use-a-platform-architecture.md
# ADR-0004 - Use a platform-oriented architecture for Gradle ## Date 2024-02-07 ## Context The Gradle code base is essentially a large monolith, without strong internal boundaries. This has a number of negative effects on productivity, including: - Unclear ownership of code. - Difficult to focus on one particular area. - Unintended coupling between areas of the code, including tests. ## Decision
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sun Feb 25 22:19:29 GMT 2024 - 4.5K bytes - Viewed (0) -
README.md
```gradle dependencies { // Pick one: // 1. Use Guava in your implementation only: implementation("com.google.guava:guava:33.2.0-jre") // 2. Use Guava types in your public API: api("com.google.guava:guava:33.2.0-jre") // 3. Android - Use Guava in your implementation only: implementation("com.google.guava:guava:33.2.0-android") // 4. Android - Use Guava types in your public API:
Plain Text - Registered: Fri May 03 12:43:13 GMT 2024 - Last Modified: Wed May 01 18:44:57 GMT 2024 - 5.9K bytes - Viewed (0) -
docs/en/docs/tutorial/body-updates.md
The examples here use `.dict()` for compatibility with Pydantic v1, but you should use `.model_dump()` instead if you can use Pydantic v2. That would generate a `dict` with only the data that was set when creating the `item` model, excluding default values. Then you can use this to generate a `dict` with only the data that was set (sent in the request), omitting default values:
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 5.6K bytes - Viewed (0) -
architecture/standards/0002-avoid-using-java-serialization.md
## Decision We do not use Java serialization. Instead, we use custom serialization where we explicitly describe how data objects should be serialized and deserialized. For internal purposes, we use binary formats for their brevity. We use the `Serializer` abstraction to separate the actual implementation of serialization from its uses. When sharing data with external tools, we use JSON. ## Status ACCEPTED
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu Feb 29 22:32:18 GMT 2024 - 2.3K bytes - Viewed (0) -
docs/en/docs/tutorial/security/simple-oauth2.md
But don't worry, you can show it as you wish to your final users in the frontend. And your database models can use any other names you want. But for the login *path operation*, we need to use these names to be compatible with the spec (and be able to, for example, use the integrated API documentation system). The spec also states that the `username` and `password` must be sent as form data (so, no JSON here).
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 12.5K bytes - Viewed (0) -
docs/en/docs/deployment/server-workers.md
* `--workers`: The number of worker processes to use, each will run a Uvicorn worker, in this case, 4 workers. * `--worker-class`: The Gunicorn-compatible worker class to use in the worker processes. * Here we pass the class that Gunicorn can import and use with: ```Python import uvicorn.workers.UvicornWorker ```
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 9.1K bytes - Viewed (0) -
docs/en/docs/tutorial/body.md
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Fri Mar 22 01:42:11 GMT 2024 - 7.3K bytes - Viewed (0) -
CREDITS
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Apr 26 06:31:35 GMT 2024 - 1.6M bytes - Viewed (0) -
docs/en/docs/deployment/docker.md
By using a pre-made container image it's very easy to **combine** and use different tools. For example, to try out a new database. In most cases, you can use the **official images**, and just configure them with environment variables. That way, in many cases you can learn about containers and Docker and re-use that knowledge with many different tools and components.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 34K bytes - Viewed (0)