You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Phase 4: Organizers preview representative attendee badges and can clear imported data explicitly #132
Part of #128. Depends on #131 and a badge template contract from #117/#104.
Problem
Rendering hundreds of badge previews at once is unnecessary and expensive, but organizers still need confidence that unusual records will fit before starting a batch. They also need an explicit way to purge imported attendee data from the current session.
Approach
Generate a small representative preview set from the normalized/selected rows and expose a clear-data action. Candidate samples include first row, longest name, rows missing optional fields, each badge role/type and a small deterministic sample.
Acceptance criteria
The preview set includes meaningful edge cases rather than simply the first N rows.
Preview generation remains bounded for large imports and does not render every attendee simultaneously.
The UI explains why each representative row was selected when useful (for example longest name or missing company).
Changing mapping/row selection/template refreshes representative previews from the current normalized data.
An explicit Clear attendee data action removes raw/normalized imported rows and returns the import flow to its initial state.
Clearing attendee data does not delete unrelated event/theme/social editor state.
No attendee row data survives a full reload unless a future explicit persistence option is implemented.
Activity