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

feat(132): clarify operator precedence #260

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

toumorokoshi
Copy link
Member

It's unclear at this point what order the various AEPs should be applied on an API endpoint, if they exist.

Adding a section to clarify this. An example of this precedence is drafted at aep-dev/aepc#60.

🍱 Types of changes

What types of changes does your code introduce to AEP? Put an x in the boxes
that apply

  • Enhancement
  • New proposal
  • Migrated from google.aip.dev
  • Chore / Quick Fix

📋 Your checklist for this pull request

Please review the AEP Style and Guidance for
contributing to this repository.

General

Additional checklist for a new AEP

  • A new AEP should be no more than two pages if printed out.
  • Ensure that the PR is editable by maintainers.
  • Ensure that File structure
    guidelines are met.
  • Ensure that
    Document structure
    guidelines are met.

💝 Thank you!

It's unclear at this point what order the various AEPs
should be applied on an API endpoint, if they exist.

Adding a section to clarify this. An example of this
precedence is drafted at aep-dev/aepc#60.
@toumorokoshi toumorokoshi requested a review from a team as a code owner January 10, 2025 17:47
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