feat(122): add missing OAS guidance - #404
Merged
Merged
Conversation
toumorokoshi
force-pushed
the
yft/122-missing-oas
branch
2 times, most recently
from
February 28, 2026 20:58
19fc15c to
a88d088
Compare
122 has guidance that is specific to proto, causing confusion when trying to apply it to OAS. Clarifying OAS guidance.
toumorokoshi
force-pushed
the
yft/122-missing-oas
branch
from
February 28, 2026 21:01
a88d088 to
c2b1c57
Compare
Member
Author
|
@thegagne would you be up for reviewing as well? As the original requestor. |
Contributor
|
Looks good. |
toumorokoshi
marked this pull request as ready for review
March 3, 2026 16:35
toumorokoshi
added a commit
to thegagne/aeps
that referenced
this pull request
Jul 25, 2026
122 has guidance that is specific to proto, causing confusion when trying to apply it to OAS. Clarifying OAS guidance.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
122 has guidance that is specific to proto, causing confusion when trying to apply it to OAS.
Clarifying OAS guidance.
🍱 Types of changes
What types of changes does your code introduce to AEP? Put an
xin the boxesthat apply
📋 Your checklist for this pull request
Please review the AEP Style and Guidance for
contributing to this repository.
General
references AEPs
correctly.
(run
make lint)💝 Thank you!