Getting builders onto 2.5.0 --> build_test 3.0.0 and test fixes
#4062
davidmorgan
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
For builder package maintainers.
When you use
build_runner2.5.0 you'll also need to update tobuild_test3.0.0, which has breaking change.Sorry about that!
build_testdepends a lot onbuild_runnerinternals, so it was not possible to keep it working exactly the same through the huge internal refactor. Hopefully, some of the changes are improvements :)See the changelog.
Here are some example fixes:
built_value: google/built_value.dart#1367source_gen: dart-lang/source_gen#761Any questions, or if any changes could help smooth the transition, I'll be happy to help :)
FAQ
Why is my test no longer reading real sources on disk?
This no longer happens automatically, for
testBuilderthe way to do it isand for
resolveSources, passnonInputsToReadFromFilesystemto read specific additional files, or passreadAllSourcesFromFilesystem: trueto read them all.If you're using
source_gen_test, make sure you have the latest release1.2.0. If you're usingexpect_errorthere is this PR out.Other Notes
The
testBuildergenerateForparameter now restricts the set of visible sources, not just the set of input sources; this is broken, if someone needs it to work please let me know and I'll fix it. However, the defaults are now much closer to a real build, so please first try removinggenerateForaltogether, like I do in thesource_genPR above.Beta Was this translation helpful? Give feedback.
All reactions