-
Notifications
You must be signed in to change notification settings - Fork 947
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
WIP - some changes to the serializers. #1300
Conversation
The get_state changes are incorporated in #1302. |
I just rebased keeping the relevant changes from before. |
} | ||
} catch (e) { | ||
console.error("Error serializing widget state attribute: ", k); | ||
console.error(`Error serializing widget state attribute ${k} (value ${state[k]})`); | ||
throw e; |
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.
I believe IE doesnt support this, right @SylvainCorlay, what's it called, template strings orso?
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.
typescript compiles this down to normal js strings.
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.
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.
👍
…a second argument, not the widget manager. We had not been calling the static _serialize_state method, and there was ambiguity with what the second argument was. This incorporates the last part of jupyter-widgets#1300.
Closed in favor of #1355, which has the last part of the above. |
This was originally part of #1294, and was reverted in c64e5f6