Restrict "non searchable" attributes in a feature request query #1372
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
|
@sklencar can you add manual test? |
|
lutraconsulting/input-manual-tests#6 Test D @sklencar or @saberraz can you also fix the input-docs to add how to configure not searchable columns? thanks |
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.
Attributes marked as
not searchableare filtered out from QgsFeature request (scope) as well as from informative text for features shown on the BrowseDataPage.Note that values for such attributes are still present in features fetched from the request (request.subsetOfAttributes() is kept unset and therefore a user see all attributes while browsing).
PR for QgsQuick will be made after this PR would be approved.
closes #1354