Skip to content

Conversation

@toumorokoshi
Copy link
Member

The AEPs incorrectly used the term "backslash".

fixes #395

🍱 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

💝 Thank you!

The AEPs incorrectly used the term "backslash".

fixes aep-dev#395
@toumorokoshi toumorokoshi requested a review from a team as a code owner December 12, 2025 05:40
Copy link
Contributor

@mkistler mkistler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! 👍

toumorokoshi and others added 2 commits December 12, 2025 08:44
Co-authored-by: Mike Kistler <mkistler@sbcglobal.net>
@rambleraptor
Copy link
Member

Are we back porting this?

Copy link
Contributor

@mkistler mkistler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! 👍

@toumorokoshi
Copy link
Member Author

Are we back porting this?

yes, I will figure out how to do that (likely a new tag)

@toumorokoshi toumorokoshi merged commit 6ddb33e into aep-dev:main Dec 12, 2025
2 checks passed
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.

Confusing / conflicting guidance in AEP-102

3 participants