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
When the query parameters (gender, role, relations) in the endpoint /corpora/{corpusname}/plays/{playname}/spoken-text are set to empty string, the entire text is returned just as if the parameter is not set at all. This behaviour seems quite implicit.
Maybe it would be good to differentiate between the parameter not being passed at all and being passed with empty string as value?
Or it be documented that the two cases produce the same result.
The text was updated successfully, but these errors were encountered:
I think it is pretty common behaviour that when you specify query parameters like this ?foo=&bar=, the processing application should treat the parameters foo and bar as if they where not set. What other behaviour would you expect? And how would it differ from omitting the query altogether?
When the query parameters (gender, role, relations) in the endpoint
/corpora/{corpusname}/plays/{playname}/spoken-text
are set to empty string, the entire text is returned just as if the parameter is not set at all. This behaviour seems quite implicit.Maybe it would be good to differentiate between the parameter not being passed at all and being passed with empty string as value?
Or it be documented that the two cases produce the same result.
The text was updated successfully, but these errors were encountered: