Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

i18n: String for CSV format is unclear #14207

Closed
rakekniven opened this issue Jan 24, 2025 · 2 comments · Fixed by #14208
Closed

i18n: String for CSV format is unclear #14207

rakekniven opened this issue Jan 24, 2025 · 2 comments · Fixed by #14208
Labels
1. to develop feature: frontend 🖌️ "Web UI" client feature: meetings 📅 Covering the webinary usecase incl. Lobby papercut

Comments

@rakekniven
Copy link
Member

const importListDescription = t('spreed', 'Content format is comma-separated values (CSV):<br/>- Header line is required and must match <samp>"email","name"</samp> or just <samp>"email"</samp><br/>- One entry per line (e.g. <samp>"John Doe","[email protected]"</samp>)',

The format of the CSV file is unclear. Should it be email,name as the headers say or name,email as the rows say?

@Antreesy
Copy link
Contributor

@nickvergessen I don't see that order is relevant for a backend. Any preferences, what should come first?

downloadParticipantsForCall returns [ 'name', 'email', 'type', 'identifier', ], we can align with that

@nickvergessen
Copy link
Member

I don't see that order is relevant for a backend.

We changed that after feedback from Viktor iirc.

downloadParticipantsForCall returns [ 'name', 'email', 'type', 'identifier'], we can align with that

lets do it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. to develop feature: frontend 🖌️ "Web UI" client feature: meetings 📅 Covering the webinary usecase incl. Lobby papercut
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants