feat: pick number, phone, email and web address when adding a question

[global-prog]

Summary

Validation for phone numbers, email addresses and numbers already exists — but it can only be reached from the input-type menu inside a short-text question that has already been created. Someone adding a question sees only "Short answer" and has no particular reason to know the rest is there.

This makes four of them pickable directly from the add-question menu:

• Number
• Phone number
• Email address
• Web address

How

Each is a preset: an ordinary short-text question created with its validation already set, applied client-side after creation. No new backend type is introduced and nothing changes on the server.

Email is deliberately a preset rather than a type of its own. Question::checkEmailType() recognises an email question only as short text carrying email validation, and the confirmation-email recipient picker depends on that test — a dedicated email type would have quietly broken it.

Web address uses the existing regex validation, since there is no dedicated URL validator. The pattern is kept simple because it has to be valid in both JavaScript and PCRE — the browser and the server each apply it — and it was checked against both engines to behave identically:

input	result
https://example.org/x	accepted
http://a.b	accepted
HTTPS://X.Y	accepted
not a url	rejected
ftp://x.y	rejected
https://has space	rejected

The preset mechanism is generic, so further presets cost only an entry in the answer type list.

Scope

• two files, frontend only
• no schema change, no API change, openapi.json unaffected

Testing

• npm run lint, npm run typecheck and prettier --check all clean
• built against current main with no errors
• checked each of the four: created from the menu, validation applied immediately without a reload, an invalid value rejected on submit, and the confirmation-email recipient picker still offering a question created via the Email preset

[Chartman123]

I don't think that we should add this overhead.

[global-prog]

Thanks for taking a look.

So that I address the right thing — do you mean the four extra entries in the add-question menu, or the preset mechanism itself?

What I was trying to fix is discoverability rather than capability. Phone, email and number validation already exist, but they can only be reached from the input-type menu inside a short-text question that has already been created, so someone adding a question has no particular reason to know they are there.

If menu length is the concern, two smaller options keep that without four new entries:

• surface the input type at add-time on the existing Short answer entry, instead of adding separate ones;
• or add Number only, as the one that is arguably a distinct question type rather than a text field with a pattern.

And if you would rather not have any of it, I am happy to close it — no objection from me. Just say which you prefer.

[Chartman123]

@global-prog I'd prefer creating a user-facing documentation/manual that describes the features. see #2643

[github-actions]

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!

(If you believe you should not receive this message, you can add yourself to the blocklist.)