Remove ReSpec clone for Arazzo #3941
Closed
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
* fix: typo spelling grammar * Update proposals/2019-07-17-Webhooks.md change ``request`` to ``requests`` Co-authored-by: Nate <37554478+servusdei2018@users.noreply.github.com> Co-authored-by: Nate <37554478+servusdei2018@users.noreply.github.com>
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"
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
* Change server-variable property to 'description' According to the spec: https://spec.openapis.org/oas/v3.1.0#server-variable-object This should validate a `description` field, not `descriptions`. * Update schema.yaml
Co-authored-by: webron <webron@users.noreply.github.com>
* Update Proposals 003 "Clarify Nullable" to approved status The proposal was adopted in OpenAPI version 3.0.3. This pull request updates the proposal with that status change. * Conformance with the standard proposal format. Changed status to 'Promoted' in accordance with the proposal template.
Add restful-react to list of implementations.
* allowEmptyValue is valid only for query parameters https://spec.openapis.org/oas/v3.1.0#parameter-object we can't move this to the dependentSchemas section because that is only valid when "schema" is present. * allowReserved only applies to parameters with a value of query https://spec.openapis.org/oas/v3.1.0#parameter-object
/info/termsOfService: https://spec.openapis.org/oas/v3.1.0#fixed-fields-0 /contact/url, email : https://spec.openapis.org/oas/v3.1.0#fixed-fields-1 implicit/authorizationUrl: https://spec.openapis.org/oas/v3.1.0#fixed-fields-24 authorizationUrl, tokenUrl, refreshUrl: https://spec.openapis.org/oas/v3.1.0#fixed-fields-24
Merging as discussed on the spec call today.
Add `schema2dts`, `whook` and `openapi-ts-sdk-builder` to implementations.
Bumps [@hyperjump/json-schema](https://github.com/hyperjump-io/json-schema) from 1.8.0 to 1.9.2. - [Commits](hyperjump-io/json-schema@v1.8.0...v1.9.2) --- updated-dependencies: - dependency-name: "@hyperjump/json-schema" dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
…p/json-schema-1.9.2 Bump @hyperjump/json-schema from 1.8.0 to 1.9.2
Update MAINTAINERS.md
operationRef is a URI-reference
Reinstate validation of JSON Schemas (and examples) in build process
Use pinned version of MAINTAINERS.md per spec version
From today's TDC call: changes related to supporting other specifications need to show that those specifications are actually being used.
We have an Appendix A that was getting treated as a numbered section, with a second Appendix A generated for references. This now correctly detects sections with "Appendix" in the name, and assigns letters appropriately. The generated references section is now Appendix B (and will always be the last appendix).
DEVELOPMENT.md: Criteria for supporting other specifications
MAINTAINERS for 3.0.0
Correctly handle appendicies in md2html
Bumps [yaml](https://github.com/eemeli/yaml) from 2.4.2 to 2.4.3. - [Release notes](https://github.com/eemeli/yaml/releases) - [Commits](eemeli/yaml@v2.4.2...v2.4.3) --- updated-dependencies: - dependency-name: yaml dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Bump yaml from 2.4.2 to 2.4.3
Add level2 headings to Security Considerations doc
Bumps [@hyperjump/json-schema](https://github.com/hyperjump-io/json-schema) from 1.9.2 to 1.9.3. - [Commits](hyperjump-io/json-schema@v1.9.2...v1.9.3) --- updated-dependencies: - dependency-name: "@hyperjump/json-schema" dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
…p/json-schema-1.9.3 Bump @hyperjump/json-schema from 1.9.2 to 1.9.3
Bumps [yaml](https://github.com/eemeli/yaml) from 2.4.3 to 2.4.5. - [Release notes](https://github.com/eemeli/yaml/releases) - [Commits](eemeli/yaml@v2.4.3...v2.4.5) --- updated-dependencies: - dependency-name: yaml dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Bump yaml from 2.4.3 to 2.4.5
typo - Inudstry Standards
Update SPECIAL_INTEREST_GROUPS.md
…abstract Remove need for separate ReSpec clone for Arazzo
ralfhandl
force-pushed
the
remove-arazzo-clone-of-respec
branch
from
22e0995
to
038b4f5
Compare
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.
Preferred order of events:
If this PR is merged first, the published OpenAPI and Arazzo specs will temporarily have an abstract with headline "Abstract" - which may be a good idea anyway 😄