Renames Router to ModularRouter to avoid conflicts with Flutter #223
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Renaming the Router from Modular to ModularRouter seems to be a better and more definitive strategy than hiding the official Flutter Router from Modular package. Eventually a project may be using both classes or add a package that uses the official one for adding routes and this could cause a bigger problem in the long term or create resistance from other developers to use Modular package as it has internal conflicts with naming from official Flutter.
After this change, the only code adjustment that had to be done in projects using modular package was to replace matching case the class Router by ModularRouter. Code worked without any further changes.
Command bellow replaces all Router calls by ModularRouter easily:
Pubspec change to test it:
Since this is an API change and I also would recommend a new version release as defined in the semver.org standard.