Skip to content

fix(generator): reject empty and unmatched Dataverse solution names - #106

Open
Bircck wants to merge 1 commit into
mainfrom
fix/solution-name-validation
Open

Bircck wants to merge 1 commit into
mainfrom
fix/solution-name-validation

Conversation

@Bircck

@Bircck Bircck commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

An empty solution selection or a misspelled name previously reached downstream metadata queries without a clear configuration error. A mixed valid/invalid selection could silently generate only part of the requested model.

Validate the selection before connecting, reject unmatched unique names after querying solutions, and normalize whitespace, empty comma entries, and duplicates for both querying and the generated solution count. Document the auth URL settings that determine redirect host and port; checks on port 3017 found no hardcoded route requiring a code change.

Validation: generator suite (111 passed, 2 existing skips), startup rejection before authentication, HTTP redirect checks on port 3017, website lint, and full production build/postbuild. Existing warnings remain unchanged. Live Dataverse and Entra sign-in were not exercised.

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

Successfully merging this pull request may close these issues.

1 participant