Per-Request Service for Context Management: Antipattern or Not?
would it be considered an antipattern to have a per-request service that holds the context of the request... user info etc?
I'm dreading adding a couple of fields and passing them around everywhere just so I cant pass them to an API call to another service
I'm dreading adding a couple of fields and passing them around everywhere just so I cant pass them to an API call to another service
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
