See also https://github.com/chewing/libchewing/pull/790#issuecomment-3698969004
Thanks to @ShikiSuen
push-lvzutovlsnnl into master See also https://github.com/chewing/libchewing/pull/790#issuecomment-3698969004
Thanks to @ShikiSuen
✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.06%. Comparing base (999ee00) to head (036d4c3).
⚠️ Report is 2 commits behind head on master.
@@ Coverage Diff @@
## master #793 +/- ##
=======================================
Coverage 92.06% 92.06%
=======================================
Files 37 37
Lines 9253 9253
=======================================
Hits 8519 8519
Misses 734 734
☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.
I think we need to add this Provide libchewing as a Swift package with the exposures of C_based APIs only. instead. This ensures that no one expects Swiftified APIs from this package (which brings extra burden to this repo). If anyone wants Swiftified APIs, he / she can make them by himself / herself.
@ -16,6 +16,7 @@ What's New in libchewing (unreleased)
- New boolean config option `chewing.sort_candidates_by_frequency` can be
@ -16,6 +16,7 @@ What's New in libchewing (unreleased)
- New boolean config option `chewing.sort_candidates_by_frequency` can be
Make sense. For me libchewing refers only to the C API but your edit makes it more clear for people unfamiliar with the history of libchewing.
Archived
Archived
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?