Skip to content

@W-22900542 264 (2026.3) VizqlDataService python sdk update - #22

Open
yunlong-zhang-sfdc wants to merge 6 commits into
mainfrom
dev/yunlongzhang/264-update
Open

@W-22900542 264 (2026.3) VizqlDataService python sdk update#22
yunlong-zhang-sfdc wants to merge 6 commits into
mainfrom
dev/yunlongzhang/264-update

Conversation

@yunlong-zhang-sfdc

Copy link
Copy Markdown
Collaborator

Description

Update the python sdk to 2026.3 including:

  • Open api schema
  • Readme, contributing and other doc
  • New workbook datasource example python

Type of Change

  • New feature
  • Documentation update

Checklist

  • I have read the contributing guidelines
  • I have added tests where applicable
  • I have updated documentation where applicable
  • I have added a clear title to this PR
  • My changes follow the project's coding style
  • I have checked for sensitive information (e.g., no secrets or passwords)

Comment thread python_sdk/CHANGELOG Outdated
yizhao1998
yizhao1998 previously approved these changes Aug 7, 2026
yunlong-zhang-sfdc and others added 2 commits August 12, 2026 08:32
Adds an opt-in --no-verify-ssl CLI flag to the examples runner so it can
target internal test hosts whose certificate chain the local trust store
cannot validate, while keeping verify_ssl=True as the SDK default.

Also labels the published-datasource flow explicitly in section headers
and the "Using ..." status line so its output is distinguishable from
the static workbook datasource flow.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
yunlong-zhang-sfdc and others added 2 commits August 12, 2026 09:14
The examples package is executable sample code, not part of the shipped
SDK surface, and its low measured coverage (~26%) was pulling the total
down and rendering a red row on the CI coverage chart. Omitting it via
[tool.coverage.run] narrows the report to the SDK proper (src, src.api)
and the test suite.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Every push to main currently triggers publish-pypi against a pyproject.toml
version that already exists on PyPI, which fails with 400 (file name reuse
is immutable). Passing skip-existing: true converts the "already exists"
case into a silent no-op so non-release merges to main stop red-X'ing CI.
New-version pushes still publish normally.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

Code Coverage

Package Line Rate Health
src 100%
src.api 96%
tests 100%
Summary 98% (1409 / 1438)

1 similar comment
@github-actions

Copy link
Copy Markdown

Code Coverage

Package Line Rate Health
src 100%
src.api 96%
tests 100%
Summary 98% (1409 / 1438)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants