You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, scripts like yarn typescript, yarn test:karma and yarn test:unit (it's an open list) run through all the packages in mui-x repo.
However in development, it doesn't make sense to run pickers tests while working on data grid and the other way around.
The goal
To have separate commands or an easy way to narrow down the scope of those scripts, similar to cli.js in material-ui repo:
The problem
Currently, scripts like
yarn typescript
,yarn test:karma
andyarn test:unit
(it's an open list) run through all the packages in mui-x repo.However in development, it doesn't make sense to run pickers tests while working on data grid and the other way around.
The goal
To have separate commands or an easy way to narrow down the scope of those scripts, similar to
cli.js
in material-ui repo:yarn test:unit
: we can use an existingcli.js
script that's currently not being used: https://github.com/mui/mui-x/blob/ebb0e3b1a4d940b02ca20abd61ade86fce9b6e94/test/cli.jsyarn test:karma
: we can reuse file pattern logic fromcli.js
and use it in https://github.com/mui/mui-x/blob/ebb0e3b1a4d940b02ca20abd61ade86fce9b6e94/test/karma.tests.jsyarn typescript
: we can uselerna run --scope
option:yarn typescript --scope "@mui/x-date-*"
for date pickersyarn typescript --scope "@mui/x-data-*"
for data gridThe text was updated successfully, but these errors were encountered: