Skip to content
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

Implement new update API for writing systems #1240

Merged
merged 5 commits into from
Nov 28, 2024

Conversation

rmunn
Copy link
Contributor

@rmunn rmunn commented Nov 15, 2024

Fix #1189.

Note that FwDataMiniLcmApi hasn't implemented the UpdateWritingSystem overload with (id, type, update), which the (before, after) method is going to end up calling. So that still needs to happen.

Note that FwDataMiniLcmApi hasn't implemented the UpdateWritingSystem
overload with (id, type, update), which is the (before, after) method
is going to end up calling. So that still needs to happen.
@rmunn rmunn self-assigned this Nov 15, 2024
@hahn-kev hahn-kev marked this pull request as draft November 15, 2024 08:20
GUID Id vs string WsId is still an issue, as is the Font/Fonts issue.
@rmunn
Copy link
Contributor Author

rmunn commented Nov 19, 2024

Decision during yesterday's team meeting: for now, Font will remain a single string and will be used to indicate the default font in LCM (DefaultFontName property). DefaultFontName is read-only in LCM, so if it changes on the CRDT side, we should instead use its new value to look up the name of a font and set the DefaultFont property in LCM, e.g.:

ws.DefaultFont = new FontDefinition("Charis SIL");

@rmunn rmunn marked this pull request as ready for review November 19, 2024 06:50
@hahn-kev hahn-kev self-requested a review November 20, 2024 07:49
Copy link
Collaborator

@hahn-kev hahn-kev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should really avoid using the WritingSystem Id property which is a Guid, maybe we mark it obsolete or something? There's a number of places where we really don't want to use it at all as there's no counterpart in Fieldworks. I left some comments to that end. Maybe we hide that field as it's really only required for Crdts.

@rmunn rmunn requested a review from hahn-kev November 27, 2024 09:25
Copy link
Collaborator

@hahn-kev hahn-kev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good to me, assuming the tests all pass go ahead and merge

@hahn-kev hahn-kev merged commit 7d002cf into develop Nov 28, 2024
11 checks passed
@hahn-kev hahn-kev deleted the feat/new-update-api-writing-systems branch November 28, 2024 06:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

implement new update api for writing systems
2 participants