-
Notifications
You must be signed in to change notification settings - Fork 40
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
Support explode in Query #1321
Comments
also this feature could cover the following uri template case:
|
@lmazuel I want to clarify the scopes for this feature. According to uri temlate design, I think we mainly have below cases.
Are they all in scope of this issue? Also there are some legacy cases which are moved from Are all workable cases in scope or only cases of cadl-ranch having in scope? |
"explode" just means this:
This is orthogonale to how you serialize an array, an object, or a primitive. You should already have those scenarios covered, independently of "explode" As of today, TypeSpec implies CSV (comma separated), it's not in scope to discuss pipe or space. DeepObject is not in scope either. Optionality or required has nothing to do with the feature (the query parameter can be optional or required, it doesn't impact the value). Explode is about the value, not the optionality or not of the query key. |
Additional note about after a comment I saw on the cadl-ranch PR, if "explode" is used on a non-array parameter, it's just ignored. The way url template RFC is written, given people could use a union like |
Support of:
to mean that the url should explode the query parameter, for instance here
foo=a&foo=b
if we pass["a","b"]
at the SDK level.TypeSpec
Spec
Implementation
The text was updated successfully, but these errors were encountered: