-
Notifications
You must be signed in to change notification settings - Fork 37
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
Consider publishing a 1.0.0 release #199
Comments
From a discussion, if we choose to rev. this to 1.0.0, doing this before package:checks is released would cause less work for the community (after that release, people will need an explicit dep on matcher in their pubspec in order to consume the package). |
We will want the The next chunk of work is to move the definitions here, and re-export them in The current sticking point is that tests of We work around this in We might be able to use a similar pattern here for matcher, it is a little ugly, but I also don't know if it's ugly enough to justify new APIs in |
This would not necessarily contain breaking changes; publishing
1.0.0
would just indicate the maturity and support of this package.The text was updated successfully, but these errors were encountered: