Remove example with missing data - #6489
Conversation
… completed in time.
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request removes a specific scatter plot visualization example from the application configuration. This is a temporary measure taken because the underlying data required for this visualization is currently unavailable, and the change may be reverted if the data ingestion process completes successfully. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request removes the scatter visualization tool example for literate population vs. population below poverty level for states in India from the scatter_vis_tool_examples.json template. There are no review comments, and I have no feedback to provide.
Description
This PR tentatively removes one of the scatter plot examples, pending whether data ingestion can be completed in time. If data ingestion makes this data available in Spanner, this PR will be discarded.
Notes
This should not be merged if data for the existing example gets in. Additionally, as it is a publicly visible change to website copy, the change should be confirmed and approved by a lead before being merged in. If required, the example can be changed.