Generation of URLs (links) in response headers or body should be customizable centrally and easily.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 505
- Forks
- 186
- PR merge metrics
- No merged PRs in 30d
Description
Description
When the service architecture includes an API proxy, then links may need to be returned in the URL-space of the proxy rather than the URL-space of the OData service generating them.
This avoids having a rewriting proxy, which impedes latency.
Today, it's not clear how to do this centrally and easily.
The library should have this as a clear extension point that does not require copy paste of significant code from library source to the exension.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing where the OData service generates URLs in response headers and bodies, then identify the central extension point used by the library. Compare the generated service URL with the API proxy URL and define what a customizable solution must cover without copying library code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100