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

AEP-122: make full resource paths always require the domain #264

Open
toumorokoshi opened this issue Jan 10, 2025 · 0 comments
Open

AEP-122: make full resource paths always require the domain #264

toumorokoshi opened this issue Jan 10, 2025 · 0 comments

Comments

@toumorokoshi
Copy link
Member

https://aep.dev/122/#full-resource-paths currently recommends that we don't include the full resource path, unless it is ambiguous:

The full resource path should not be used for cross-API references where the owning API is clear; it is only used if a field refers to resources in multiple APIs where ambiguity is possible.

This makes resource paths much less useful, since it does not allow a the simple pattern of using a relative appending strategy for non-qualified domains, and an absolute path otherwise.

Should we make this a should on fully-qualified paths?

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

No branches or pull requests

1 participant