-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
fix(web): remove remaining references to dart:html
#12601
Conversation
dart:html
@Lyokone - it appears these references also need to be removed (according to the open issue):
Other than that, it LGTM. |
Still looking into cleaning this conditional import EDIT: found the doc: https://dart.dev/interop/js-interop/package-web#conditional-imports |
|
||
// Clear the children in our container so we can add an element to click | ||
target.children.clear(); | ||
for (int i = 0; i < target.children.length; i++) { |
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 don't think this will work. The length will reduce every call, so maybe only n/2 items will be removed.
Maybe better to do a do/while
?
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 think we only have a length of 1, but maybe it's isn't the case in some places.
Updated the example app code here: #12614
* fix(web): remove remaining references to dart:html * remove conditionnal import * fix conditional import
Description
Replace this paragraph with a description of what this PR is doing. If you're modifying existing behavior, describe the existing behavior, how this PR is changing it, and what motivated the change.
Related Issues
closes #12597
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]
).This will ensure a smooth and quick review process. Updating the
pubspec.yaml
and changelogs is not required.///
).melos run analyze
) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?