From 40b1abdf5453623d241448ee7f20d6706a30491b Mon Sep 17 00:00:00 2001 From: Alex Stephen Date: Fri, 31 May 2024 11:29:27 -0700 Subject: [PATCH] resource path changes --- aep/general/0180/aep.md.j2 | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/aep/general/0180/aep.md.j2 b/aep/general/0180/aep.md.j2 index 0bc6055f..3381a26c 100644 --- a/aep/general/0180/aep.md.j2 +++ b/aep/general/0180/aep.md.j2 @@ -104,15 +104,15 @@ Existing fields and messages **must not** have their type changed, even if the new type is wire-compatible, because type changes alter generated code in a breaking way. -### Changing resource names +### Changing resource paths -A resource **must not** change its [name][aep-122]. +A resource **must not** change its [path][aep-122]. Unlike most breaking changes, this affects major versions as well: in order for a client to expect to use v2.0 access a resource that was created in v1.0 or vice versa, the same resource name **must** be used in both versions. -More subtly, the set of valid resource names **should not** change either, for +More subtly, the set of valid resource paths **should not** change either, for the following reasons: - If resource name formats become more restrictive, a request that would