Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Feature proposal: [BasePath] attribute
See original GitHub issueThe routing attributes in RestEase serve a similar function to those of ASP.Net MVC. In the latter, it’s possible to put a Route[] attribute on the interface, which then gets prepended to the routes of all its service operations.
It would be helpful if RestEase offered a similar attribute (possibly BasePath?) for interfaces. I realise that the entire base URL can be specified when creating the client, but sometimes it’s not practical to put paths in this URI - for example where the host address comes from configuration and hosts multiple endpoints.
Happy to contribute a PR if this is considered in-scope.
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yep happy to do so. My IL is, uh, rudimentary, I’m sure I’ll have questions!
Gosh, sorry 😊. For work I sidestepped it for my domain problem (REST hosted in Service Fabric). I’d been meaning to decouple it from the specifics and open a PR (even bought a book on IL), but… life got in the way.
As penance, I’ll see if work will let me open source RestEase.ServiceFabric as an extension library. Thanks again for an awesome library, my colleagues and I are loving it!