-
Notifications
You must be signed in to change notification settings - Fork 162
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
feat(idb): Update to newer API #350
Conversation
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.
At a quick glance, this one looks like it may not be binary compatible. Aside: we should add MiMa to the build if possible.
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.
In 1.x, you can introduce the new defs and top-level members, but you cannot remove the old ones. You have to deprecate them instead.
@armanbilge I'm thinking to just reschedule this to 2.0 rather than try to massage compatibility. wdyt? |
Yup, agree! |
rebased |
IDB DomString constants have been removed from browser API and replaced by raw String values. Remove IDB DOMString constants that are no more supported and lead to an UndefinedBehaviorError. Add these constants in a typesafe way.
Thanks so much for the PR @mprevel and sorry for the big turnaround time in getting this merged. |
I was a bit busy and did not follow what happened to this PR lately. |
IDB DomString constants have been removed from browser API and replaced by raw String values.
Remove IDB DOMString constants that are no more supported and lead to an UndefinedBehaviorError.
Add these constants in a typesafe way.