- Sort Score
- Result 10 results
- Languages All
Results 1 - 8 of 8 for slug (0.14 sec)
-
api/maven-api-core/src/main/java/org/apache/maven/api/Packaging.java
import org.apache.maven.api.annotations.Nonnull; import org.apache.maven.api.model.PluginContainer; /** * Interface representing a Maven project packaging. * <p> * TODO: define how to plug in new packaging definitions using the SPI. * the packaging are currently defined by Maven 3 {@code Provider<LifecycleMapping>} * * @since 4.0.0 */ @Experimental @Immutable
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Fri Apr 12 10:50:18 GMT 2024 - 1.9K bytes - Viewed (0) -
docs/tr/docs/history-design-future.md
Geçmişte oluşturulan pek çok araç **FastAPI**'a ilham kaynağı olmuştur. Yıllardır yeni bir framework oluşturmaktan kaçınıyordum. Başlangıçta **FastAPI**'ın çözdüğü sorunları çözebilmek için pek çok farklı framework, <abbr title="Eklenti: Plug-In">eklenti</abbr> ve araç kullanmayı denedim.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Fri Mar 22 01:42:11 GMT 2024 - 4.7K bytes - Viewed (0) -
docs/fr/docs/history-design-future.md
J'ai évité la création d'un nouveau framework pendant plusieurs années. J'ai d'abord essayé de résoudre toutes les fonctionnalités couvertes par **FastAPI** en utilisant de nombreux frameworks, plug-ins et outils différents.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Fri Mar 22 01:42:11 GMT 2024 - 4.9K bytes - Viewed (0) -
common-protos/k8s.io/apimachinery/pkg/runtime/generated.proto
optional string apiVersion = 1; // +optional optional string kind = 2; } // Unknown allows api objects with unknown types to be passed-through. This can be used // to deal with the API objects from a plug-in. Unknown objects still have functioning // TypeMeta features-- kind, version, etc. // TODO: Make this object have easy access to field based accessors and settors for // metadata and field mutatation. //
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 4.2K bytes - Viewed (0) -
docs/en/docs/features.md
* **No compromise** with databases, frontends, etc. But easy integration with all of them. ### Unlimited "plug-ins" Or in other way, no need for them, import and use the code you need. Any integration is designed to be so simple to use (with dependencies) that you can create a "plug-in" for your application in 2 lines of code using the same structure and syntax used for your *path operations*. ### Tested
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 9.3K bytes - Viewed (0) -
docs/en/docs/history-design-future.md
I have been avoiding the creation of a new framework for several years. First I tried to solve all the features covered by **FastAPI** using many different frameworks, plug-ins, and tools.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Fri Mar 22 01:42:11 GMT 2024 - 4.1K bytes - Viewed (0) -
docs/pt/docs/history-design-future.md
Eu estive evitando a criação de um novo _framework_ por vários anos. Primeiro tentei resolver todas as funcionalidades cobertas por **FastAPI** usando muitos _frameworks_, _plug-ins_ e ferramentas diferentes.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Fri Mar 22 01:42:11 GMT 2024 - 4.5K bytes - Viewed (0) -
docs/en/docs/tutorial/handling-errors.md
But when you register an exception handler, you should register it for Starlette's `HTTPException`. This way, if any part of Starlette's internal code, or a Starlette extension or plug-in, raises a Starlette `HTTPException`, your handler will be able to catch and handle it. In this example, to be able to have both `HTTPException`s in the same code, Starlette's exceptions is renamed to `StarletteHTTPException`:
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Fri Mar 22 01:42:11 GMT 2024 - 9.1K bytes - Viewed (0)