Repository navigation
Conversation
Tested against Tableau Cloud: only a comma breaks a filter value. Ampersands, colons and square brackets match exactly, because TSC URL-encodes the query string. The docstrings said all five characters were unusable and cited a server-documented wildcard feature that the REST API only documents for the like operator on user and group names. Co-Authored-By: Claude Code <noreply@anthropic.com>
Co-Authored-By: Claude Code <noreply@anthropic.com>
Before REST API 3.7 TSC does not URL-encode the query string, so an ampersand ends the filter. Say so, and scope the Tableau Cloud wildcard example to Cloud. Co-Authored-By: Claude Code <noreply@anthropic.com>
Prefix, suffix and middle * matched in Equals filters on workbook names (Tableau Cloud) and project names (REST API 3.31). Co-Authored-By: Claude Code <noreply@anthropic.com>
Co-Authored-By: Claude Code <noreply@anthropic.com>
QuerySet.__iter__ caught every ServerResponseError but only handled 400006, so any other error (for example 400065 for a filter value with a comma) ended the loop with no items instead of raising. Co-Authored-By: Claude Code <noreply@anthropic.com>
This branch has not been deployed
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.
Summary
&,:,[and]match exactly. From REST API 3.7, TSC URL-encodes the query string, so&is safe. Earlier versions do not encode it, and&ends the filter.likeoperator on user and group names.*workaround for a comma, with a client-side check for exact matches. In testing,*matched at the start, end, and middle of anEqualsvalue on workbook names (Tableau Cloud) and project names (REST API 3.31). The REST API documentation does not describe this or say which versions support it.QuerySet.__iter__caught everyServerResponseErrorbut only handled400006, so any other error ended the loop with no items. It now re-raises everything except400006. For example,for wb in server.workbooks.filter(name="a, b")raised nothing and yielded nothing; it now raises400065, aslist(),len()and.get()already did.Behavior change: code that loops over a queryset and relied on a failed request returning no items now gets the exception.
Refs #1200, #1431
Related
🤖 Generated with Claude Code