Afform - Optimize Get by checking type #21316
Merged
Conversation
This file contains 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
… custom data Sometimes afforms are fetched by type, e.g. `cv api4 Afform.get +w type=search` Previously this would load all html files and custom data groups before discarding the ones not of type search. Now it will skip irrelevant files.
|
(Standard links)
|
|
Tested this works well merging |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Overview
Makes Afform get API calls more efficient if "type" is specified in the where clause, e.g. when fetching forms of type "search".
Before
Sometimes Afforms are fetched by type, e.g.
cv api4 Afform.get +w type=searchPreviously this would load all html files and custom data groups before discarding the ones not of type search.
After
Fetching by type skips unnecessary file and custom data loading.