We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow namespaces (and it's accompanying path) to be defined along with related details (e.g. routes and/or nested namespaces).
The 可愛い!(scaffold <etc>) was meant to support nesting due to rustless implementing Nesting and ApiHandler for both Api and Namespace.
可愛い!(scaffold <etc>)
Nesting
ApiHandler
Api
Namespace
A rough example is given below (does include dependency injection).
fn test<'a>(client: Client<'a>, example: String) -> Response<'a> { // ... } fn other_test<'a>(client: Client<'a>) -> Response<'a> { // ... } fn main() { let application = 可愛い!( namespace (first/example:string) [ get (one) -> test; get (two) -> test; ] namespace (second/example) [ get (one) -> other_test; ] get (last/example:string) -> test; ); // ... }
To be honest, I'm not a huge fan of the brackets but there needs to be some way to tell when the current namespace ends.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Allow namespaces (and it's accompanying path) to be defined along with related details (e.g. routes and/or nested namespaces).
The
可愛い!(scaffold <etc>)
was meant to support nesting due to rustless implementingNesting
andApiHandler
for bothApi
andNamespace
.A rough example is given below (does include dependency injection).
To be honest, I'm not a huge fan of the brackets but there needs to be some way to tell when the current namespace ends.
The text was updated successfully, but these errors were encountered: