Skip to content

fix(102): slash, not backslash, in API name #398

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.

Sign up for GitHub

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

Merged
toumorokoshi merged 3 commits into from
Dec 12, 2025
Merged

fix(102): slash, not backslash, in API name #398

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
cf168c8
fix(102): slash, not backslash, in API name
toumorokoshi Dec 12, 2025
ffcc4aa
Update aep/general/0102/aep.md.j2
toumorokoshi Dec 12, 2025
33705d1
address code review
toumorokoshi Dec 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions aep/general/0102/aep.md.j2
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,10 +25,11 @@ can still ensure uniqueness can be used. For example APIs served at

The API Name:

- **must** only uses valid domain name characters as specified in
- **must** only use valid domain name characters as specified in
[RFC 1035](https://datatracker.ietf.org/doc/html/rfc1035#section-2.3.1), or a
backslash `[.-a-z0-9/]`)
- **must** use all lower case.
slash `[.-a-z0-9/]`)
- **must** use all lowercase.
- **must** start with a lowercase letter.
- **should not** use path prefixes that could also be misconstrued as a
resource collection (e.g. `apis.examples.com/users`)

Expand Down