Is there any plan to expose all child objects of Workbook/Worksheet? - Feature Request

Open
#164 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
api

Research direction

Start by reviewing the library's existing Workbook and Worksheet entry points and comparing their exposed objects with the corresponding workbook XML (.twb). Define the supported read-only surface needed to inspect worksheets, dashboards, tabs or views, fonts, colors, and backgrounds; done means those aspects can be audited without relying on release-sensitive XML traversal.

Written by the indexing model from the issue text.

Description

enhancement

Hello All,

It would be great to have the ability to enforce UI Standards (even if Write access is not supported at least to have read access) by exposing Worksheets of the Workbook. It will help to help to audit Enterprise UI/UX standards and report to the respective Workbook owner. For example Fonts, Color, Background. Simply expecting all aspects of Worksheet and Dashboard (Tab/View) to generate Enterprise Standards compliance report. Now it is possible to traverse the XML (.twb) but it is risky as it is subject change on every release.

Thank you

Dominant language
Python
Stars
363
Forks
183
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tableau/document-api-python

All issues in tableau/document-api-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.