Forms custom endpoints and headers #167
Open
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.
Adds the ability to specify the endpoint on the Form components as a property, as well as on the LoginRoute and LoginLink. Essentially, all components that would call a config-defined endpoint will instead call the given endpoint. If no endpoint is provided, the behaviour remains the same.
Additionally, adds a third optional
headersparameter for all Form components that have support for theonSubmitfunction. This parameter is an object that can be used to manually set some headers before calling the API/back-end intergration. Something like this was asked about in #151.Fixes #120