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

Add support for data slice update in charts #2338

Open
1 of 7 tasks
FabienLelaquais opened this issue Dec 16, 2024 · 2 comments · May be fixed by #2390
Open
1 of 7 tasks

Add support for data slice update in charts #2338

FabienLelaquais opened this issue Dec 16, 2024 · 2 comments · May be fixed by #2390
Assignees
Labels
🖰 GUI Related to GUI ✨New feature 🟧 Priority: High Must be addressed as soon 🔒 Staff only Can only be assigned to the Taipy R&D team

Comments

@FabienLelaquais
Copy link
Member

FabienLelaquais commented Dec 16, 2024

Description

Multi-trace charts rely on a single data property, which is a limitation.

Solution Proposed

Make data an indexed property.

Acceptance Criteria

  • If applicable, a new demo code is provided to show the new feature in action.
  • Integration tests exhibiting how the functionality works are added.
  • Any new code is covered by a unit tested.
  • Check code coverage is at least 90%.
  • Related issue(s) in taipy-doc are created for documentation and Release Notes are updated.

Code of Conduct

  • I have checked the existing issues.
  • I am willing to work on this issue (optional)
@FabienLelaquais FabienLelaquais added 🖰 GUI Related to GUI 🟧 Priority: High Must be addressed as soon ✨New feature 🔒 Staff only Can only be assigned to the Taipy R&D team labels Dec 16, 2024
@FredLL-Avaiga FredLL-Avaiga self-assigned this Dec 23, 2024
Copy link
Contributor

github-actions bot commented Jan 7, 2025

This issue has been labelled as "🥶Waiting for contributor" because it has been inactive for more than 14 days. If you would like to continue working on this issue, please add another comment or create a PR that links to this issue. If a PR has already been created which refers to this issue, then you should explicitly mention this issue in the relevant PR. Otherwise, you will be unassigned in 14 days. For more information please refer to the contributing guidelines.

@github-actions github-actions bot added the 🥶Waiting for contributor Issues or PRs waiting for a long time label Jan 7, 2025
@FredLL-Avaiga FredLL-Avaiga removed the 🥶Waiting for contributor Issues or PRs waiting for a long time label Jan 7, 2025
@jrobinAV
Copy link
Member

jrobinAV commented Jan 7, 2025

To add my two cents to the topic, when communicating about this indexed data topic, instead of data slice, I would suggest using something else like data layer or data stratum or any better naming since data slicing already means something in data processing.

FredLL-Avaiga pushed a commit that referenced this issue Jan 10, 2025
@FredLL-Avaiga FredLL-Avaiga linked a pull request Jan 10, 2025 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🖰 GUI Related to GUI ✨New feature 🟧 Priority: High Must be addressed as soon 🔒 Staff only Can only be assigned to the Taipy R&D team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants