feat(env): add customapi group with list, create, generate-openapi - #176
Open
zekelinAlex wants to merge 1 commit into
Open
feat(env): add customapi group with list, create, generate-openapi#176zekelinAlex wants to merge 1 commit into
zekelinAlex wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a
customapinoun group undertxc envfor working with Custom APIs in the connected environment.Three commands:
listshows registered Custom APIs with optional--searchfiltering,createregisters a new Custom API including request parameters and response properties, andgenerate-openapiemits an OpenAPI 3.0 spec (JSON) for one or all Custom APIs, either to stdout or a file via--output.While wiring up create through the changeset pipeline I noticed
ChangesetApplierwas building entities without attribute metadata, so typed values (optionsets, money, lookups) went to Dataverse as raw JSON primitives. It now prefetches entity metadata for record CREATE/UPDATE ops and converts values the same way the direct record service does.Closes #98