| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Yes, this is a possible solution, if breaking changes in minor versions are considered that bad :) |
Sorry, something went wrong.
|
Hey, @PeterStaev. Regarding the breaking changes policy, our team is committed to following the SemVer Specification, which means that all changes in a minor version should be introduced in a backward-compatible manner. With that said, Nathanael's suggestion is a good one. Would you mind adjusting your PR according to his proposal, so that we can proceed with the technical review? Thanks for jumping on this issue! |
Sorry, something went wrong.
|
@etabakov , updated and removed the breaking changes. Removed from the above description as well :) |
Sorry, something went wrong.
|
Alot |
Sorry, something went wrong.
|
test |
Sorry, something went wrong.
|
test |
Sorry, something went wrong.
|
@PeterStaev Looking good now and I have merged the PR. Thanks! |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
PR Checklist
What is the current behavior?
Current file-system methods for read/write files are synchronous which makes the UI thread block if a big file is read/written.
What is the new behavior?
True async methods have been added that use native code inside tns-core-modules-widgets execute the read/write operations in a separate thread.
Closes #2239 .