You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
https://aep.dev/122/#full-resource-paths currently recommends that we don't include the full resource path, unless it is ambiguous:
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?
The text was updated successfully, but these errors were encountered: