Collect editable name forms with stress marks #18

New issue

Open

opened 2026-11-01 20:11:37 +00:00 by viacheslavshuka · 0 comments

viacheslavshuka commented

2026-11-01 20:11:37 +00:00

Owner

Outcome

Testers need names suitable for acknowledgments. Collect given name and surname in nominative and genitive forms during registration, then allow ordinary profile edits.

Use Russian-first localized forms. Keep all four fields explicit instead of inferring surname boundaries from a combined name.

Acceptance criteria

Registration requires the four preferred-name fields. Users can edit nominative values prefilled from rating metadata.
Users enter genitive forms themselves. Each corresponding field offers Copy nominative form without automatic declension.
Identical nominative and genitive forms are valid without an equality error, exception checkbox, or additional confirmation.
A helper lets users select the stressed vowel. Directly typed and pasted stress marks also remain usable.
Stored, displayed, and copied names preserve stress marks. Quorum does not infer pronunciation or move a mark based on rating spelling.
Explanatory sentences use nominative Ива́н Петро́в for who participated and genitive Ива́на Петро́ва after wording meaning with the help of.
The form previews the user's own values in grammatically appropriate sentences. It does not illustrate genitive with an accusative construction.
A successful edit preserves account identity, rating verification, attendance, and restrictions. Future acknowledgment generation can read the current forms.
Failed validation or a rejected write preserves visible input and does not partially update the four fields.
Profile editing occurs on the website. Bot navigation opens that form without introducing a second name-editing workflow.

Validation design

Use indeclinable surnames, identical forms, pasted combining stress marks, and multipart names to expose equality checks and destructive normalization. Test the helper by keyboard and touch. Verify that failed saves preserve input and that changing names does not alter stable identity. Do not infer grammatical correctness or pronunciation from external spelling.

Dependencies

#14: Authenticate Telegram users through protected Quorum sessions. Provides authenticated registration progress and account-scoped writes.
#7: Create the React application with locked frontend tooling. Provides localized form controls and typed browser integration.

## Outcome Testers need names suitable for acknowledgments. Collect given name and surname in nominative and genitive forms during registration, then allow ordinary profile edits. Use Russian-first localized forms. Keep all four fields explicit instead of inferring surname boundaries from a combined name. ## Acceptance criteria - Registration requires the four preferred-name fields. Users can edit nominative values prefilled from rating metadata. - Users enter genitive forms themselves. Each corresponding field offers Copy nominative form without automatic declension. - Identical nominative and genitive forms are valid without an equality error, exception checkbox, or additional confirmation. - A helper lets users select the stressed vowel. Directly typed and pasted stress marks also remain usable. - Stored, displayed, and copied names preserve stress marks. Quorum does not infer pronunciation or move a mark based on rating spelling. - Explanatory sentences use nominative Ива́н Петро́в for who participated and genitive Ива́на Петро́ва after wording meaning with the help of. - The form previews the user's own values in grammatically appropriate sentences. It does not illustrate genitive with an accusative construction. - A successful edit preserves account identity, rating verification, attendance, and restrictions. Future acknowledgment generation can read the current forms. - Failed validation or a rejected write preserves visible input and does not partially update the four fields. - Profile editing occurs on the website. Bot navigation opens that form without introducing a second name-editing workflow. ## Validation design Use indeclinable surnames, identical forms, pasted combining stress marks, and multipart names to expose equality checks and destructive normalization. Test the helper by keyboard and touch. Verify that failed saves preserve input and that changing names does not alter stable identity. Do not infer grammatical correctness or pronunciation from external spelling. ## Dependencies - [#14: Authenticate Telegram users through protected Quorum sessions](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/14). Provides authenticated registration progress and account-scoped writes. - [#7: Create the React application with locked frontend tooling](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/7). Provides localized form controls and typed browser integration. ## Related work - [#27: Complete registration through verified rating-profile control](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/27) - [#68: Generate alphabetical tester acknowledgment lists](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/68)

viacheslavshuka referenced this issue

2026-11-01 20:11:44 +00:00

Complete registration through verified rating-profile control #27

viacheslavshuka referenced this issue

2026-11-01 20:12:34 +00:00

Generate alphabetical tester acknowledgment lists #68

viacheslavshuka added the