You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: clarify username formats, ProjectLeader-as-group, and filter special-char behavior (#1854)
* docs: clarify username formats, ProjectLeader-as-group, and filter special-char behavior
Bundles three long-standing docs gaps flagged in stale issues:
#993 - users.add example used a fake short username with no explanation
that `name` is the server auth identifier (email on Cloud, SAM@Domain on
AD-backed Server), not the person's display name. Rewrote the users.add
docstring intro to describe the required formats per auth scheme, split
the example into a Cloud invocation and an AD invocation, and added
matching guidance to UserItem.name.
#1067 - projects.update_permissions had no examples, so callers had no
guide for the common "assign group as Project Leader" case. Added an
example that shows constructing a PermissionsRule with grantee=<group>
and capability=ProjectLeader, plus a note that update_permissions is a
full replacement (call populate_permissions first if preserving
existing rules).
#1200 - the REST filter grammar treats ',', '&', ':', '[' and ']' as
delimiters and the server does not support escaping, so
`filter(name="T(L-F,SZ&V-MY)")` fails with 400065 for any name
containing those characters. Documented the constraint on the Filter
class docstring and on QuerySet.filter, along with the working
wildcard workaround (Equals with '*' substituted).
No behavior change. Docs only.
Closes#993, #1067, #1200.
* docs: cite wildcard-filter server version requirement
The Equals-operator wildcard workaround for special characters requires
Tableau Cloud May 2023 or Tableau Server 2022.1.14 (per the REST API
"Filtering and Sorting" docs). Older servers reject `*` as a literal, so
readers on those need to know before copying the example.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* docs: ASCII em dashes, drop dead docs link, soften AD claim
Three fresh-eyes findings:
- Replace Unicode em dashes (U+2014) in filter.py and users_endpoint.py
docstrings with ASCII `--` or `;`, matching the repo's ASCII-only
convention that other docstrings follow.
- query.py referenced docs/filter-sort.md, which lives on the gh-pages
branch and does not exist in an installed package. Swap for the
published URL so a `help()` reader can actually reach the doc.
- Soften the AD username claim in users_endpoint.py: a bare
SAMAccountName's resolution depends on the AD configuration, so
"typically will not resolve" was stated more strongly than the
surrounding server-behavior guidance warranted.
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
0 commit comments