Skip to content

Consider renaming oAuth Flows Object from 'flow' to 'flows' #967

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

Closed
MikeRalphson opened this issue Mar 7, 2017 · 2 comments
Closed

Consider renaming oAuth Flows Object from 'flow' to 'flows' #967

MikeRalphson opened this issue Mar 7, 2017 · 2 comments
Milestone

Comments

@MikeRalphson
Copy link
Member

This is probably a non-starter at this stage, but it is one of the rare examples in the specification of a singular noun being used to describe a collection. Changing this would draw attention to the fact this area of the specification has changed. See also #953 re: example/examples.

@ePaul
Copy link
Contributor

ePaul commented Mar 7, 2017

I think now (before the final release of 3.0) is the perfect time to do this change.
Any implementer who has already implemented it as flow has a tiny change to do.

@webron
Copy link
Member

webron commented Mar 7, 2017

It looks like an oversight and a remnant from the previous version. We'll consider it.

webron added a commit that referenced this issue Apr 23, 2017
@webron webron mentioned this issue Apr 23, 2017
@webron webron closed this as completed Apr 26, 2017
@handrews handrews added this to the v3.0.0-rc1 milestone Feb 8, 2024
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

No branches or pull requests

4 participants