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.

Sign up for GitHub

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

Jump to bottom

Library dependencies should not be too restrictive #111

Closed
navispatial opened this issue Jun 2, 2022 · 2 comments
Closed

Library dependencies should not be too restrictive #111

navispatial opened this issue Jun 2, 2022 · 2 comments
Labels
🌎 geodata Related to the code package "geodata" 🌐 geobase Related to the code package "geobase" 🌐 geocore Related to the code package "geocore" refactoring

Comments

@navispatial
Copy link
Member

Check dependencies on pubspec.yaml, ensure that not too specific version requirement (but of course minimum required version).
@navispatial navispatial added 🌐 geocore Related to the code package "geocore" 🌎 geodata Related to the code package "geodata" refactoring 🌐 geobase Related to the code package "geobase" labels Jun 2, 2022
@navispatial
Copy link
Member Author

For example geocore had:

dependencies:
  equatable: ^2.0.3

But it's better to define it as

dependencies:
  equatable: ^2.0.0

When using dart pub upgrade latest version (here equatable with 2.0.3 get loaded) even with the latter definition.

@navispatial
Copy link
Member Author

Checked on versions 0.9.0 of both geocore and geodata. In geobase nothing to check.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🌎 geodata Related to the code package "geodata" 🌐 geobase Related to the code package "geobase" 🌐 geocore Related to the code package "geocore" refactoring
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@navispatial