docs: note vf() view filters are exact-match only - #1835
Open
jacalata wants to merge 1 commit into
Open
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
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 note near the shared
ImageRequestOptions/PDFRequestOptions/CSVRequestOptionssection explaining thatvf()view filters are exact-match only, with a pointer to the Tableau REST API docs and mentioning the workbook-parameter workaround for range filtering.Followup to closed PR #1813, which had tried to add operator support (
gt:,lt:etc.) tovf()client-side — verified against server code that thevf_*REST endpoint parses values by data type with no operator recognition, silently dropping filters likevf_sales=gt:1000. The client can't fix this; a note is the right response.Test plan
ImageRequestOptionsandPDFRequestOptions..." intro and the "For more information about filtering and sorting..." link