-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
oauth2MetadataUrl #3625
oauth2MetadataUrl #3625
Conversation
…branches (#2597) Signed-off-by: Mike Ralphson <[email protected]>
* fix: v2.0 maintainers and version/date Signed-off-by: Mike Ralphson <[email protected]> * Add some largely non-visible SEO improvements to the rendered spec Signed-off-by: Mike Ralphson <[email protected]>
* nuke proposal prefixes * Add YYYY-MM-DD prefixes to proposal documents Signed-off-by: Mike Ralphson <[email protected]>
* fix: md2html/build.sh specify bash in shebang Signed-off-by: Mike Ralphson <[email protected]> * fix: changes for abstract title in md2html.js Signed-off-by: Mike Ralphson <[email protected]>
Signed-off-by: Mike Ralphson <[email protected]>
…mas) (#2614) * Add test cases for valid and invalid top-level schemaObject types Signed-off-by: Mike Ralphson <[email protected]> * Update workflow actions to node 14 Signed-off-by: Mike Ralphson <[email protected]>
Makes the workflow trigger match the comment, thus giving people more time to add agenda items
#2157: Update schema to validate refs in headers of encoding objects
Add accessible meetings slide to agenda template
This makes metaschema consistent with the 3.0.x spec. Refs #2666
* fix: typo spelling grammar * Update proposals/2019-07-17-Webhooks.md change ``request`` to ``requests`` Co-authored-by: Nate <[email protected]> Co-authored-by: Nate <[email protected]>
generated via: perl -MYAML::XS -MJSON::MaybeXS -we'$YAML::XS::Boolean="JSON::PP"; print Dump(JSON::MaybeXS->new->decode(do { local $/; <> }))' input.json > output.yaml
* minor simplification of v3.1 schema "if the X property is present, then apply this constraint to property X" can be simplified by simply stating the constraint for property X. * add missing constraint to "header" https://spec.openapis.org/oas/v3.1.0#headerObject * allowEmptyValue and allowReserved don't make sense for headers * collapse single-item "enum"s in "cookie" and "header" to "const"
If the wrong type is used for a particular piece of data, then a bare "required" will validate as true, causing the "if" clause to be true, which can lead to confusing errors when the "then" schema then fires, instead of the error occurring at a higher position in the schema.
https://spec.openapis.org/oas/v3.1.0#pathTemplating "The value for these path parameters MUST NOT contain any unescaped “generic syntax” characters described by [[!RFC3986]]: forward slashes (/), question marks (?), or hashes (#)."
2nd attempt at this. Adding ".md" suffix. Intended to be a place for all our SIGs to better define who they are, how to join, expectations, etc.
- name is required (for parameter) - the map under content must contain only one entry as per https://spec.openapis.org/oas/v3.1.0#fixed-fields-9
Project's url https://github.com/OverSpeedIO/koa2-oas3 shows 404. Can't find the project through google either. Looks like the project closed.
Also normalize whitespace in table headers
Signed-off-by: Mike Ralphson <[email protected]>
Bump yaml from 2.4.0 to 2.4.1
Bumps [@hyperjump/json-schema](https://github.com/hyperjump-io/json-schema) from 1.7.2 to 1.7.3. - [Commits](https://github.com/hyperjump-io/json-schema/commits) --- updated-dependencies: - dependency-name: "@hyperjump/json-schema" dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
…son-schema-1.7.3 Bump @hyperjump/json-schema from 1.7.2 to 1.7.3
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 1.3.1 to 1.4.0. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v1.4.0/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
Proposing updates to the TSC processes around membership.
Bump vitest from 1.3.1 to 1.4.0
Bumps [markdown-it](https://github.com/markdown-it/markdown-it) from 14.0.0 to 14.1.0. - [Changelog](https://github.com/markdown-it/markdown-it/blob/master/CHANGELOG.md) - [Commits](markdown-it/markdown-it@14.0.0...14.1.0) --- updated-dependencies: - dependency-name: markdown-it dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
…-14.1.0 Bump markdown-it from 14.0.0 to 14.1.0
clarifying the provisional period
Looks fair , we should update the meta schema soemthing around this line but question to @handrews should it goes to a dedicated schema 3.2 ... |
Like this?
|
ty @karenetheridge for spotting
Update actions used in respec workflow
The meta schema can be updated later on, it doesn't need to be part of this change. |
Co-authored-by: Lorna Jane Mitchell <[email protected]>
Update GOVERNANCE.md
Replaced a longer draft features section with a proposed proposal process
Update MAINTAINERS.md
Hi, the longer this mini PR stays unresolved the bigger the mess I create. Sorry. |
@AxelNennker I'l take a look and see if I can untangle it! |
I can't guess what happened here, but I don't see your original commits anywhere so I can't recover them. As you can tell from our pull request queue, it's not unusual for pull requests to be open for longer periods of time, so it would be good to understand what happened here so you can contribute this change (and hopefully many others) safely! The fastest route forward is to recreate the pull request (I'm sorry, I realise this wasn't the first time you proposed this change, but I'm in support of us accepting it so let's persevere). My tips for success:
I'm closing this pull request because I feel like I have to - we can't merge it as it is - but I'm looking out for it's replacement! |
Add oauth2MetadataUrl to oauth2 allows the client to download the OAuth2 metadata to download the RFC8414 OAuth2 metadata.
Fixes #3595