Add headers option to defaultAJAXparams #50
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
so I'm not sure with credentials option is going to be something we're going to want to have on by default |
|
Oh, yeah, definitely not. I was messing with it and didn't realize that it updated this pull request. :) |
Open
|
Is there any progress on merging this? If the |
|
ah. @ollyollyollyltd that is why it doesnt work... been searching why.. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I was not able to use the XMLHttpRequest headers option until I added a
headers: {}default to thedefaultAJAXparamsobject. It seems that the option was getting lost when the other options were added to theajaxParamsvariable in the for loop.npm run buildchanged the dist files a bit, feel free to not take those changes.