Closed ditman closed 4 months ago
This would help us smoothly land the following PRs in order:
I had to do something similar with my js-interop package for GIS, see here:
@a14n is there any problem that I'm not seeing by maintaining the >=0.5.1 <2.0.0 range? It seems I didn't need any code changes in the JS-interop code itself, only in the examples (that are assuming 1.0.0 already)
If we go back to web: ">=0.5.1 <2.0.0"
and dart pub downgrade
then there are analysis errors on innerHTML
assignments in examples like:
A value of type 'JSString' can't be assigned to a variable of type 'String'. Try changing the type of the variable, or casting the right-hand type to 'String'.
That's why I changed that. But if it makes your migration easier I can publish a temporary version. I just don't want to have this kind of issue with the final release.
8.0.0-dev.4 published
there are analysis errors on
innerHTML
assignments in examples
But example
is not part of the lib
that people use, right?
Why not make the example
an actual app, so it has its own pubspec.yaml
? That way we can set the dependency to web: ^1.0.0
there (that's what I did with the GIS web sdk at least).
I haven't looked deep at how examples work/are built in this package, but I can set example
as a separate app, if it helps!
Another way of supporting the old innerHTML behavior in web:>=0.5.1 <2.0.0
is with something like this :)
I agree with examples being their own app if they cause issues
Forget my concern about examples. It's fine. Let me know if I can publish a final version of 8.0.0.
Revert "bump to web:^1.0.0"
This reverts commit 696b254341bc75a407d827c2835f55d961301959.