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

Make it more clear when authorization is required or not #1971

Closed
turt2live opened this issue Apr 20, 2019 · 0 comments · Fixed by #2090
Closed

Make it more clear when authorization is required or not #1971

turt2live opened this issue Apr 20, 2019 · 0 comments · Fixed by #2090
Assignees
Labels
clarification An area where the spec could do with being more explicit client-server Client-Server API

Comments

@turt2live
Copy link
Member

Currently there's a tiny bit of bold text that says when authorization is required, and nothing when it isn't. We should be clearer about when an access_token is to be (not) provided

@turt2live turt2live added clarification An area where the spec could do with being more explicit client-server Client-Server API labels Apr 21, 2019
@turt2live turt2live added this to Nice to have clarifications in Matrix 1.0 workflow May 25, 2019
@turt2live turt2live moved this from Clarifications TODO to To add to spec in Matrix 1.0 workflow Jun 3, 2019
@turt2live turt2live moved this from To add to spec to In progress in Matrix 1.0 workflow Jun 6, 2019
@turt2live turt2live self-assigned this Jun 6, 2019
Matrix 1.0 workflow automation moved this from In progress to Done Jun 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification An area where the spec could do with being more explicit client-server Client-Server API
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

1 participant