Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(genericjsonapi): add url_configs keyword arg #475

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

vergenzt
Copy link

@vergenzt vergenzt commented Sep 25, 2024

This change allows headers & other adapter kwargs to be restricted to specific URL patterns!

Also included two other minor fixes.

I believe added unit tests for all new behavior.

Let me know what you think!

docs/adapters.rst Outdated Show resolved Hide resolved
docs/adapters.rst Outdated Show resolved Hide resolved
@vergenzt vergenzt force-pushed the vergenzt/add-request-headers-by-origin branch 3 times, most recently from 1a76df9 to 99bf011 Compare October 13, 2024 00:46
@vergenzt vergenzt changed the title feat: add request_headers_by_origin config to GenericJSONAPI feat: add url_configs to GenericJSONAPI Oct 13, 2024
@vergenzt vergenzt force-pushed the vergenzt/add-request-headers-by-origin branch from 99bf011 to 5852e6f Compare October 15, 2024 14:06
@vergenzt vergenzt changed the title feat: add url_configs to GenericJSONAPI feat(genericjsonapi): add url_configs keyword arg Oct 15, 2024
@vergenzt vergenzt force-pushed the vergenzt/add-request-headers-by-origin branch 3 times, most recently from dac1662 to ffce495 Compare October 15, 2024 16:28
@vergenzt vergenzt force-pushed the vergenzt/add-request-headers-by-origin branch from ffce495 to bd51bb3 Compare October 15, 2024 16:53
@vergenzt vergenzt force-pushed the vergenzt/add-request-headers-by-origin branch from bd51bb3 to c42165c Compare October 15, 2024 17:03
@vergenzt vergenzt marked this pull request as ready for review October 15, 2024 18:47
@vergenzt
Copy link
Author

Hey @betodealmeida! I made a couple changes in approach to this PR. Would you mind re-reviewing and letting me know if you have any feedback or concerns? 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants