morebits: Use csrfToken in mw.user.tokens #712
Merged
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.
We need to migrate our token usage properly (#615, noted in #616) but one simple step is moving from
mw.user.tokens.get('editToken')
tomw.user.tokens.get('csrfToken')
. UsingcsrfToken
in favor ofeditToken
was done back in 2015/2016 with the move away fromaction=tokens
tometa=tokens
. BotheditToken
andcsrfToken
have been provided in themw.user.tokens
object for quite some time, and the former is finally being deprecated (see T233442). The presence of theedittoken
attribute in xml responses is unchanged.