Retire liblcm refusals once FieldWorks pins a liblcm with #410/#413/#414
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
Research direction
Read LiblcmRefusals, LiblcmRefusalSweepTests and UnstorablePropertyTests, then check the FieldWorks SilLcmVersion pin and whether a liblcm release includes fixes #410, #413 and #414. After that release is pinned, rerun the sweep and reduce the refusal rules to cases liblcm still throws, keeping DroppedProperty/OnDropped for remaining refusals. The issue says control characters still need handling under liblcm#415.
Written by the indexing model from the issue text.
Description
SIL.TextEditing.LCModel refuses text properties and values that liblcm 11.0.0-beta0180 throws on (LiblcmRefusals, reported through OnDropped). The liblcm fixes sillsdev/liblcm#410, #413 and #414 remove almost all of those throws.
Evidence, from a local build of the three PRs combined (-p:SilLcmVersion=11.0.0-stack410-413-414.gb9b80fa, packed into the local feed):
- Nothing is refused by property number any more: 50, 129, 150–155, 159 and 160 all load.
- Most integer range rules and the string rules for properties 1–5, 7, 130, 133, 145 and 146 are unnecessary: 7457 integer and 9178 string cases are "liblcm loads, rules refuse".
- There are 0 cases of "liblcm throws, rules accept".
- 9 refusal tests fail as expected: the 5 in
LiblcmRefusalSweepTestsand 4 inUnstorablePropertyTests.
When FieldWorks pins a liblcm release with those fixes:
- Bump
SilLcmVersion. - Rerun the sweep and shrink
LiblcmRefusalsto what still throws. The sweep is the single source of truth. - Keep
DroppedProperty/OnDroppedfor anything left. Control characters are still deleted on save; see sillsdev/liblcm#415.
Blocked on a liblcm release and the FieldWorks pin.
- Dominant language
- C#
- Stars
- 0
- Forks
- 0
- Avg merge
- 1h 43m
- Merged PRs (30d)
- 43
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from sillsdev/SIL.TextEditing
-
Playground selection bar: comes back after Apply or scrolling while focus is in the Markdown paneOpen
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
sillsdev/SIL.TextEditing#175 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
sillsdev/SIL.TextEditing#167 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
sillsdev/SIL.TextEditing#164 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sillsdev/SIL.TextEditing#137 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
sillsdev/SIL.TextEditing#133 ·
Maintainers usually reply within 1 day
All issues in sillsdev/SIL.TextEditing
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
BEagle1984/silverback#280 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
-
Status: Needs Triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
PSAppDeployToolkit/PSAppDeployToolkit#2392 ·
Maintainers usually reply within 1 day
-
needs attention untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet#3666 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
MicrosoftLearning/eShopOnWeb#466 ·