It would be really created to add to a workspace the API definition that is primary used by the workspace.
That would be enable IntelliSense for the URL, Query-Parameter, and body.
An example of something similar like this, is the URL input of the graph API explorer:
But this idea can be complex. Because an API definition can have much information. For example, in ODATA you also know the model of your body. So, you can supply IntelliSense there two.
There are also some actions that can't be found in the API definition. For example, OData is a global standard, and the standard defines the query parameter, but they are not defined in the API definition (metadata document)
I think in open API it defines both. Also the body and the query parameter. Also all url paths.
It would be really created to add to a workspace the API definition that is primary used by the workspace. That would be enable IntelliSense for the URL, Query-Parameter, and body.
An example of something similar like this, is the URL input of the graph API explorer:
But this idea can be complex. Because an API definition can have much information. For example, in ODATA you also know the model of your body. So, you can supply IntelliSense there two.
There are also some actions that can't be found in the API definition. For example, OData is a global standard, and the standard defines the query parameter, but they are not defined in the API definition (metadata document)
I think in open API it defines both. Also the body and the query parameter. Also all url paths.