Adding an artifact offered a "New dialect" chip that swapped in three
more fields -- name, country, language -- and minted a dialect on the
way to creating the artifact. Now that a group defines its dialects on
its own screen, that path is a second, worse way to do the same thing:
it creates a dialect as a side effect of an unrelated action, in a form
where the fields belong to neither entity clearly, and with no sight of
what the group has already defined beyond a row of chips.
Drop it. The chip row is now exactly the dialects that exist, and
selectedDialectId changes meaning from "null = create a new one" to
"null = nothing picked yet" -- which the FAB rejects alongside the other
required fields, rather than falling through to creating something.
A group with no dialects yet gets a line saying so and pointing at the
group screen, instead of a lone chip that opens a form.
addArtifact loses the three TextFieldStates and existingDialectId for a
single dialectId, and with them the branch that called addDialect and
threaded its id back in. Validation is now one condition rather than one
per path.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Kgothatso NgakoandClaude Opus 5
e14be2d187