Slug Uniqueness Logic - Scope to features.json instead of entire Knowledge Graph

[lymarrie]

Description

Currently, during dynamic dev mode, PagesJS validates that each slug value (which powers the getPath function) is unique with respect to the entire Yext Knowledge Graph.

This means, if a Knowledge Graph has two entities with slug = index.html, PagesJS will throw an error; even if one of those entities isn't actually in use for the site during local development. This makes it difficult to use dynamic mode for accounts that may be multi-site (meaning more than one entity will have the same slug).

Suggested solution

Ideally, PagesJS should only validate slug uniqueness against entities defined in features.json, as opposed to the entire Knowledge Graph.

Alternative

No response

Additional context

No response

Validations

• Check that there isn't already an issue that requests the same feature to avoid creating a duplicate.

[benlife5]

Yext CLI issue, not pagesJS
Spruce ticket here