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.
Proposal: Response-only mapper
See original GitHub issueOur current options:
Currently, whenever an Endpoint does not have a request object, you either have to:
a) Create your own custom mapping logic - creating inconsistencies in your architecture, or
b) Create an Endpoint using Empty Request Objects (like the built-in EmptyRequest struct). This has it’s own sets of problems, like for example having options like ToEntity which makes no sense in this context, or having a request parameter in the HandleAsync method which will never be used
Was this an oversight and/or simply not been implemented yet, or is there a good reason this is currently not supported?
What I would like is this:
Issue Analytics
- State:
- Created a year ago
- Comments:11 (11 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
I am! 🎉
BetweenNames#4911 (Made this post, which I referenced in my last comment 😛 ))
You’re doing a tremendous job - it’s a sunday for darn sake!