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

docs(spec): indicate in detail how Channel Item Object field resolves #714

Closed
wants to merge 1 commit into from

Conversation

char0n
Copy link
Collaborator

@char0n char0n commented Feb 7, 2022

Refs #612

This PR targets targets two things:

  1. As we now have reusable Channel Item Objects stored in Components.channels, there is no reason why the description of the $ref field should explicitly only allow referencing external definition of the Channel Item Object (in different document) and not the internal one

  2. Second change targets the unspecified rules of resolution for the $ref field. I've added explicit mention of JSON Reference specification which the resolution of the $ref field is based on.

@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 7, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@char0n
Copy link
Collaborator Author

char0n commented May 4, 2022

Succeeded by #779

@char0n char0n closed this May 4, 2022
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

Successfully merging this pull request may close these issues.

1 participant