Alternate "syntax" for routing.
See original GitHub issueJust a wild idea. How about allowing routing like get("path", ::someMethod)
and the parameters of that method are annotated the same way the fields of parameter classes are now annotated.
That way you don’t have to declare a class for just one or two simple parameters and you get a very natural looking routing style.
Also this would be quite familiar to users of springfox.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:13 (1 by maintainers)
Top Results From Across the Web
Alternate Routes - TCP/IP Implementation and Operations Guide
You can use the ROUTE command in IPv4 or IPv6 networks to manually define multiple routes to a common destination such that access...
Read more >Alternate Static Route - Cisco Community
I have configure Static Route configured so that alternate path can be used if any link direct from location 'A' is down. What...
Read more >Chapter 12. Configuring Policy-based Routing to Define ...
Configuring Policy-based Routing to Define Alternative Routes ... The nmcli connection add command creates a NetworkManager connection profile.
Read more >Understanding Loop-Free Alternate Routes for IS-IS | Junos OS
That is, a neighbor whose shortest path to the destination traverses the routing device is not used as a backup route to that...
Read more >An introduction to Wouter: A React Router alternative
Client side routing (CSR) is similar to server side routing (SSR), except CSR is handled by the browser. In a typical web app,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah, I see how putting that info in the path string is suboptimal. Yet I think that the idea of keeping the location of parameters in the route and type, documentation and default values in the method is sound. I’ll try to come up with a better way of expressing that info.
I haven’t gotten around to start beyond the initial proof of feasibility. I am currently on other projects. If you think you can get something clean on the rails feel free to contribute.