-
Notifications
You must be signed in to change notification settings - Fork 25
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
RFC: New question type "MultipleFileQuestion" #1780
Comments
Does this allow you to rename the files as well by supplying an |
Currently this is not intended. For this use-case you would have to delete the file and upload it again with the correct name. |
But doesn't that go against the general caluma API where you can simply supply the same mutation with new values to change an existing resource? mutation changeTitle {
SaveTextQuestion(input: { slug: "some-question", label: "cool new label" }) {
question {
id
}
}
} The only 2 places where I had to implement or work with file uploads (TCS and alexandria) both required the renaming of files. If it isn't much effort it might be worth doing it now, otherwise I guess we wait until its requested. |
Sorry for correcting you, but what @StephanH90 asks is indeed possible with the current backend implementation: If you provide a new name for a given file ID, it will rename it internally and do the work needed so the file is moved in Minio as well. See the |
Oh sorry, for the incorrect feedback then! But this feature will not be part of the current ember-caluma implementation for now. |
So what's the ember-caluma release plan for this? Just not ready jet, or is it delayed on purpose? |
When using file questions, it is often desired that more that one file can be uploaded. Currently this is only possible in Caluma using TableQuestions, which doesn't yield a good UX when the table form consists of just one FileQuestion.
We'd propose to add a new question type "MultipleFileQuestion" which is very similar to the existing "FileQuestion", but allows uploading more than one file.
The API could look like this:
FileAnswer (existing, just for reference)
Request:
Response:
MultipleFileAnswer
Request:
Response:
The text was updated successfully, but these errors were encountered: