-
-
Notifications
You must be signed in to change notification settings - Fork 126
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
Audit DataGrid
public API in preparation for 0.x => 2.0
#458
Conversation
I believe from a releaser standpoint we need to set |
Need to pass a |
It is |
I'm not convinced we should go that road. It was not needed earlier and we also decide it was not needed for JupyterLab (although dependency cycles are still to be removed). I'm in favor to bump all packages for v2. But going forward in v2 branch I don't see the benefit to use fixed version as most of the time is will bumped packages for no reasons. |
The diff now contains a lot of changes to datagrid, which doesn't seem related to the title of this PR? |
Yeah, I should make two PRs, probably. Basically the name |
DataGrid
public API in preparation for 0.x => 2.0
cc: @martinRenou @ibdafna |
80bf433
to
bcd7e8d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thank you
This is because initially it was bumped to 1.0-alpha but then the decision changed to move directly to 2.0 in: jupyterlab/lumino#458
This is because initially it was bumped to 1.0-alpha but then the decision changed to move directly to 2.0 in: jupyterlab/lumino#458
This is because initially it was bumped to 1.0-alpha but then the decision changed to move directly to 2.0 in: jupyterlab/lumino#458
In this PR:
2.0.0-alpha.6
Notification
class forDataGrid
instances that useCellEditor
into the latter's namespace:CellEditor.Notification