Skip to content
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

Revert also down to meta 1.8.0? #26

Closed
monsieurtanuki opened this issue Jun 2, 2023 · 4 comments
Closed

Revert also down to meta 1.8.0? #26

monsieurtanuki opened this issue Jun 2, 2023 · 4 comments

Comments

@monsieurtanuki
Copy link
Contributor

Because every version of flutter_test from sdk depends on meta 1.8.0 and crop_image >=1.0.8 depends on meta ^1.9.1, flutter_test from sdk is incompatible with crop_image >=1.0.8.

@deakjahn
Copy link
Owner

deakjahn commented Jun 2, 2023

I don't normally use meta for anything, so I don't know immediately where it was introduced at all. Maybe one of your PRs? :-) I would suggest to remove it altogether.

@deakjahn
Copy link
Owner

deakjahn commented Jun 2, 2023

  1. I don't think that image setter hurts anybody.

  2. Same about the two rectangle helper functions. If you really want to hide them, my usual solution is just to make the extension name private in the same source file, eg. _RectExtensions. That's completely enough to hide it from the outside, although I don't think that it harms anything even if exposed.

@monsieurtanuki
Copy link
Contributor Author

@deakjahn You added meta at least 2 years ago:
Capture d’écran 2023-06-02 à 18 18 27

As I come from Java, I do think it's much cleaner to use meta annotations, without having to play with file names, class names or method names.

@deakjahn
Copy link
Owner

deakjahn commented Jun 2, 2023

Really? I wonder why... Now as I check it, it was in the dev dependencies part, only got moved up. Still doesn't answer why it was needed in the first place. :-) Yep, it was down there in the initial commit. I probably cloned another package to start this one, that's why.

Anyway, I'll remove it now. I only partly agree with you in this, namely, if it's an annotation that's part of the core language itself, then OK. But not to rely on an outside package just to do something that's not even necessary... And, after all, the underscore is Dart's own mechanism for visibility, not a hack but part of the language itself... :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants