Joscha Krutzki
Joscha Krutzki
Just to clear some responsibilities regarding the backend, it: - cannot say what the user can do until the user is logged in (we don't know about local roles, groups)...
Ok, its just bit more work (make sure caching works) What about the parameter name, `add_roles=True` ?
.. not to forget the option request to get the query parameter for the options request
The downside is adding query parameters is quite hacky, also we have to remove it if we want to get rid of options request to improve performance.
So you want to make two different requests, one for the participator role, one for the current user?
`options /process` returns the options for the current user `options /process/?role=` returns the options for the specific role
We should fix the meta api to make this more simple. At the moment we have the following Meta Api Field types with References: Resource: ``` data format: resource url...
> Its also handy if we not only reference sheet type but also resource types. > For this we would have to change the metaapi. What do you think? We...
Instead of restricting characters a more sophisticated email detection would be nicer.
Also the backend instead of the frontend would be the better place to handle issues like "is this an email or login name"