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

[discussion] Preparing v6 #3287

Closed
40 of 41 tasks
flaviendelangle opened this issue Nov 26, 2021 · 8 comments
Closed
40 of 41 tasks

[discussion] Preparing v6 #3287

flaviendelangle opened this issue Nov 26, 2021 · 8 comments
Labels
breaking change discussion umbrella For grouping multiple issues to provide a holistic view v6.x

Comments

@flaviendelangle
Copy link
Member

flaviendelangle commented Nov 26, 2021

This is an umbrella issue that centralizes and lists all the potential improvements that we can consider in MUI X v6. The potential improvements being listed here require breaking changes. We do intend to ship v6 in the coming months. We plan, as much as possible, to release the next major features in minor versions without breaking changes.

Same issue for MUI Core v6: mui/material-ui#30660

Infrastructure

Data Grid packages

Publicly deprecated APIs.

Columns

As discussed in #4769

Rows

Cells

Filtering

Sorting

Editing

Pagination

Density

Row Grouping

Virtualization / Rendering

Detail Panel

Keyboard navigation

Styling

General events topics

Focus management

Error management

Slots

@flaviendelangle flaviendelangle added the status: waiting for maintainer These issues haven't been looked at yet by a maintainer label Nov 26, 2021
@oliviertassinari oliviertassinari added breaking change v6.x discussion and removed status: waiting for maintainer These issues haven't been looked at yet by a maintainer labels Nov 26, 2021
@oliviertassinari oliviertassinari changed the title [Discussion] Preparing v6 [discussion] Preparing v6 Nov 27, 2021
@flaviendelangle flaviendelangle pinned this issue Dec 7, 2021
@oliviertassinari oliviertassinari added the umbrella For grouping multiple issues to provide a holistic view label Dec 17, 2021
@flaviendelangle
Copy link
Member Author

flaviendelangle commented Apr 27, 2022

@alexfauquette could you add a line in the list above to match the comment // TODO v6: remove once we stop ignoring events fired from portals ? I did not follow exactly what has to be done

@m4theushw
Copy link
Member

Rename the filterPanelOperatorAnd translation key filterPanelOperator

I didn't understand this one.


I added:

@flaviendelangle
Copy link
Member Author

Rename the filterPanelOperatorAnd translation key filterPanelOperator

I didn't either 😆 , but there is a TODO, @alexfauquette maybe

Rename GridFilterModel['linkOperator'] to GridFilterModel['logicOperator']

Yes logicOperator is probably more accurate

Use React.useState to track the cells in edit mode, instead of the grid's state

Could you describe that one / link an issue ?

@alexfauquette
Copy link
Member

Rename the filterPanelOperatorAnd translation key filterPanelOperator

I think it refers to this TODO

  filterPanelOperators: 'Operator', // TODO v6: rename to filterPanelOperator

@flaviendelangle
Copy link
Member Author

@alexfauquette oh that's funny, the script updating the locale files is putting the comment in the wrong place
It considers it as a group title

  // Filter panel text
  filterPanelAddFilter: 'إضافة مرشِح',
  filterPanelDeleteIconLabel: 'حذف',
  filterPanelLinkOperator: 'عامل منطقي',
  filterPanelOperators: 'عامل',

  // TODO v6: rename to filterPanelOperator
  filterPanelOperatorAnd: 'و',
  filterPanelOperatorOr: 'أو',
  filterPanelColumns: 'الأعمدة',
  filterPanelInputLabel: 'القيمة',
  filterPanelInputPlaceholder: 'ترشِيح قيمة',

@mbrookes
Copy link
Member

Column reordering disabled by default? It's inconsistent with the row reordering. And should columns have the six-dot icon to indicate "re-orderability", the same as rows?

@mbrookes
Copy link
Member

mbrookes commented Apr 28, 2022

Don't show the keyboard focus indicator when a cell is not keyboard focused. At the moment a cell gets a blue outline when it is clicked. Not sure that's so much of a breaking change as a bug fix, bit it's enough of a change in behaviour that it probably deserves to wait for v6.

@m4theushw
Copy link
Member

Column reordering disabled by default? It's inconsistent with the row reordering. And should columns have the six-dot icon to indicate "re-orderability", the same as rows?

@mbrookes It's not consistent because, although both are "reordering", they have different use cases. Column reordering is meant to only change the order of the columns that the user, using the grid, sees. The new order might be persisted, by saving the session, but in essence it's only for visualization. The row reordering is meant to reorder rows and save this new order in a database, so it can be presented in the same order in another page, that might not be using the grid. It's not enabled by default because if the backend is not prepared it has no use. If it was enabled by default, it would be too easy to mess with the saved order since rows change more often than columns. If a new row is added we can't trust the saved order anymore.

And should columns have the six-dot icon to indicate "re-orderability", the same as rows?

Maybe, but we're already fighting to fit the column menu icon. We still need to support column reordering in mobile so the icon could go into the columns panel.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking change discussion umbrella For grouping multiple issues to provide a holistic view v6.x
Projects
None yet
Development

No branches or pull requests

6 participants