-
Notifications
You must be signed in to change notification settings - Fork 215
add flutter sdk support to build_resolvers #2501
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
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.
What should our testing strategy be for this? I suspect we don't want to bring in a Flutter SDK on travis?
I think we do essentially have to do that. I want to try and make that only happen for this test suite though. |
var color = classDefinition.getField('color'); | ||
|
||
if (_isFlutter) { | ||
expect(color.type.name, equals('Color')); |
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.
[nit] I think we typically haven't used equals
in this repo
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.
🤷♂️ not worth rerunning the ci imo
Fixes #733
We always start with the Dart sdk, but now if we can find the
_embedder.yaml
file for the flutter sdk then we add any libraries found in that to the Dart sdk before summarization.This has the effect of making any flutter libraries available to builds that are using the flutter sdk.
WIP: Still thinking the best way to test this, we probably have to download the whole flutter sdk and run a test using that.Test has been added now.