-
Notifications
You must be signed in to change notification settings - Fork 15
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
docs: add thoughts on future design #157
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #157 +/- ##
==========================================
- Coverage 96.27% 96.03% -0.24%
==========================================
Files 28 20 -8
Lines 3191 2898 -293
==========================================
- Hits 3072 2783 -289
+ Misses 119 115 -4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
README.md
Outdated
library from within a Flutter app. Published to pub.dev, usage is optional by | ||
developers. | ||
|
||
Mos interesting code is in the `library` directory. There is also |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mos interesting code is in the `library` directory. There is also | |
Most interesting code is in the `library` directory. There is also |
README.md
Outdated
library from within a Flutter app. Published to pub.dev, usage is optional by | ||
developers. | ||
|
||
Mos interesting code is in the `library` directory. There is also |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mos interesting code is in the `library` directory. There is also | |
Most interesting code is in the `library` directory. There is also |
patch/README.md
Outdated
and we intend to move to a system whereby `patch` is responsible for including | ||
its own hash in the patch file and validating during application. | ||
|
||
In that world we might end up with two hashes. One who's purpose is to validate |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In that world we might end up with two hashes. One who's purpose is to validate | |
In that world we might end up with two hashes. One whose purpose is to validate |
patch/README.md
Outdated
and we intend to move to a system whereby `patch` is responsible for including | ||
its own hash in the patch file and validating during application. | ||
|
||
In that world we might end up with two hashes. One who's purpose is to validate |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In that world we might end up with two hashes. One who's purpose is to validate | |
In that world we might end up with two hashes. One who's purpose is to validate |
No description provided.