Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Resolve multiple sphinx warnings #3787

Merged
merged 5 commits into from
Feb 3, 2025
Merged

Conversation

dangotbanned
Copy link
Member

@dangotbanned dangotbanned commented Feb 3, 2025

Tried for a few hours to fix but not interested anymore

#3787 (comment)
@dangotbanned
Copy link
Member Author

Now the only warnings left are the one's that'll be fixed by (vega/vega-lite#9524)

altair.vegalite.v5.schema.core.LegendConfig:169: WARNING: Inline literal start-string without end-string. [docutils]
altair.vegalite.v5.schema.core.LegendConfig:169: WARNING: Inline literal start-string without end-string. [docutils]
altair.vegalite.v5.schema._config.LegendConfigKwds:169: WARNING: Inline literal start-string without end-string. [docutils]
altair.vegalite.v5.schema._config.LegendConfigKwds:169: WARNING: Inline literal start-string without end-string. [docutils]

@dangotbanned dangotbanned marked this pull request as ready for review February 3, 2025 21:05
@dangotbanned dangotbanned enabled auto-merge (squash) February 3, 2025 21:05
@dangotbanned dangotbanned merged commit 7fce53d into main Feb 3, 2025
25 checks passed
@dangotbanned dangotbanned deleted the fix-sphinx-warnings branch February 3, 2025 21:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant