OptionalactionOptionalcomponentComponent to use for this route.
This backend, regardless of what value you set here will be used automatically if RouteHandleDescription.backend_url is supplied a value. This is done to ensure that context is correctly set.
Use BackendLayout
This layout should have its route path set to :pk. Value :pk is a
placeholder that is dynamic. PK for the unfamiliar stands for
"Primary Key" which is a unique ID used by databases. Its recommended
usage here is two-fold: denotes a single item and if you need to use
path /add (used for new object creation, see DetailLayout) you
can.
Use DetailLayout.
Use History.
Use Redirect.
Use List.
Use Markdown.
Use Settings
Use Ticket.
OptionalhandleArbitrary data for this route.
Available keys for use within a routes handle.
Optionalbackend_url?: stringURL base for the backend.
Optionalmetadata?: apiRootMetadataCached apiRootMetadata from the backend at RouteHandleDescription.backend_url. This key must not be populated by the end-user when declaring routes. The key is automatically populated by dynamicRouter
Optionalurl_post?: stringThis key is only used by Redirect layout.
URL to perform a HTTP/POST against.
Optionalurl_redirect?: stringThis key is only used by Redirect layout.
URL to redirect to.
OptionalhydrateComponent to use for hydration.
Optionalidid to use for this route.
Is this route an index route? This value must always be set to true
OptionalloaderLoader to use for this route. Only specify a loader if there is data that must be fetched.
Use djangoLoader.
Use djangoMetadataLoader.
Use githubLoader.
OptionalrevalidateShould the loader data be re-validated on a navigation event.
This Description describes index routes that are used by routesFromObject to build the RouteObjects for the UI.
Since
0.13.0