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
To exclude all the operation imports and bound operations from the generated code, you are required to pass a comma-separated list of all the operation imports or bound operations. This can be tedious in a case where you have lots of bound operations or operation imports.
The solution is to have an option like this --excluded-operation-imports * or --excluded-bound-operations * that one can use to exclude all the operation imports or bound operations.
The text was updated successfully, but these errors were encountered:
ElizabethOkerio
changed the title
Support a "*" option that one can use to exclude all operation imports and bound-operations when using the odata-cli
Support a "*" option that one can use to exclude all operation imports and bound operations at once when using the odata-cli
Mar 23, 2022
To exclude all the operation imports and bound operations from the generated code, you are required to pass a comma-separated list of all the operation imports or bound operations. This can be tedious in a case where you have lots of bound operations or operation imports.
The solution is to have an option like this
--excluded-operation-imports *
or--excluded-bound-operations *
that one can use to exclude all the operation imports or bound operations.The text was updated successfully, but these errors were encountered: