fix: getProviders recognizes application/json accept header #156
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR #155
fix: content routing provider data handling and test cases
Description
Fixed the content routing implementation to ensure proper handling of provider data and JSON content types. All test cases are now passing across different environments (Node.js, Browser, WebWorker).
Key improvements:
Content-Type: application/json
headersTest Results:
Note: The 2 pending tests are related to cache TTL functionality, which is expected behavior.
Notes & open questions
None - all test cases are passing as expected across environments.
Change checklist