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

Improve editing capabilities of Taipy tables #1777

Open
1 of 6 tasks
FlorianJacta opened this issue Sep 11, 2024 · 0 comments
Open
1 of 6 tasks

Improve editing capabilities of Taipy tables #1777

FlorianJacta opened this issue Sep 11, 2024 · 0 comments
Labels
🖰 GUI Related to GUI ✨New feature 🟩 Priority: Low Low priority and doesn't need to be rushed

Comments

@FlorianJacta
Copy link
Member

FlorianJacta commented Sep 11, 2024

Description

I'm looking for a way to enable immediate editing for all editable columns or cells of a table. Instead of clicking the pencil icon for each cell I want to edit, I would like to have a single button that makes all cells in the table ready for editing.

This was asked by a user.

Requested Features

  1. Single Button for Editing All Cells:

    • A feature to enable editing mode for all editable cells in a table with a single click, rather than activating each cell individually.
  2. Row-Wise Editing and Accept Button:

    • Ability to edit multiple cells in a row simultaneously and then click an "accept" button to update an item in CosmosDB for the entire row, instead of confirming each cell's edit independently.
  3. Master Accept Button for All Changes:

    • A master "accept" button that commits all changes made across the entire table, updating the corresponding CosmosDB items for each modified row.

Current Limitation

These capabilities are not available in the existing Table element.

Environment

Taipy: develop/4.0

Suggested Solution

Consider adding these options to Taipy.

Acceptance Criteria

  • Ensure new code is unit tested, and check code coverage is at least 90%.
  • Create related issue in taipy-doc for documentation and Release Notes.
  • Check if a new demo could be provided based on this, or if legacy demos could be benefit from it.
  • Ensure any change is well documented.

Code of Conduct

  • I have checked the existing issues.
  • I am willing to work on this issue (optional)
@FlorianJacta FlorianJacta added ✨New feature 🖰 GUI Related to GUI 🟩 Priority: Low Low priority and doesn't need to be rushed labels Sep 11, 2024
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: Low Low priority and doesn't need to be rushed
Projects
None yet
Development

No branches or pull requests

1 participant