charts_flutter doesn't work with flutter master about charts HOT 6 CLOSED

This is the example app, which demonstrated what a developer would do, and thus it's pubspec uses published deps.

from charts.

cc @cbbraun @lorrainekan

from charts.

It looks like what is happening here is caused by charts_flutter's dependency on charts_common is pulling from the published version instead of the latest code in charts_common. Changing the pubspec.yaml to point to the charts_common code in file will cause these errors to go away.

@mit-mit what is the best practice going forward? Always publishing charts_common every time we make a change doesn't seem to be the right way. Do we change pubspec.yaml to point to the file path? This means before we publish we would have to be careful about changing it back.

Issue #35 seem to be unrelated from this error and I am reopening that one.

from charts.

Yes, you have to publish them both if one depends on another, and common has a change. Pub always depends via published deps.

from charts.

Sure, that makes sense. But what we are seeing here is fetching the latest code here in github and trying to run it. The latest charts_flutter here is asking for charts_common from pub instead of from code.

It doesn't seem sustainable to publish charts_common every time we do a github sync?

from charts.

charts_common 0.2.0 and charts_flutter 0.2.0 both published.

from charts.