Restructure repo #4
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This adds in all the dargon2 sister plugins (dargon2, dargon2_core, dargon2_interface, dargon2_flutter, dargon2_flutter_mobile, dargon2_flutter_web, and dargon2_flutter_platform_interface) together in a monorepo-style structure.
Why?
All the plugins are intrinsically related and it makes simultaneous editing, testing, and feature addition much easier
Similarly, issue testing, feature addition, and general work will be made much easier, especially within the deeper dependencies like dargon2_core, dargon2_interface, or dargon2_flutter_platform_interface as I can quickly see any cascading changes.
No Breaking Changes
This is just me moving files from separate repositories to one unified one. There are ZERO changes to the plugin code with this PR, all that is done is restructuring. Any use within applications will continue as-is without any developer changes