mt-homonymy-support #2

Manually merged
lexonomy merged 7 commits from mt-homonymy-support into master 2 years ago
matic_t commented 2 years ago
Collaborator
There is no content yet.
ozbolt was assigned by matic_t 2 years ago
lkavcic was assigned by matic_t 2 years ago
matic_t added 4 commits 2 years ago
Poster
Collaborator

Probably best if both of you check it out.
Ožbolt for prevention and Luka so we both can speed up understanding of whole stack.

Basically we're adding support for the example in vsms1.xml file. It's already in schema so we just had to provide support in editor.

https://lexonomy.cjvt.si/5pdds79p/ - link to plugin used on dictionary

Probably best if both of you check it out. Ožbolt for prevention and Luka so we both can speed up understanding of whole stack. Basically we're adding support for the example in vsms1.xml file. It's already in schema so we just had to provide support in editor. https://lexonomy.cjvt.si/5pdds79p/ - link to plugin used on dictionary
matic_t added 1 commit 2 years ago
matic_t added 1 commit 2 years ago
matic_t added 1 commit 2 years ago
Collaborator

First of all, I did not test the code, I just went over the changes.

About the code, there are two mistakes:

  • homonomy_list_getter in common_accessors is only used once. This is fine, but the way I imagined it is that if this kind of functionality is only used once, than implement it inside the class (this time its EditHomonymy). Then later if needed to avoid code duplication refactor stuff out of the class and in common_accessors. But that is fairly subjective point and you can decide to do it another way :)
  • second one, if your IDE does white spaces this way, than create a big commit with only white space changes and than work from there. This is again not so important, but makes git blame and commits themselfs much less readable.

Otherwise, yes, everything looks nice and clean, gg :)

First of all, I did not test the code, I just went over the changes. About the code, there are two mistakes: * `homonomy_list_getter` in `common_accessors` is only used once. This is fine, but the way I imagined it is that if this kind of functionality is only used once, than implement it inside the class (this time its `EditHomonymy`). Then later if needed to avoid code duplication refactor stuff out of the class and in common_accessors. But that is fairly subjective point and you can decide to do it another way :) * second one, if your IDE does white spaces this way, than create a big commit with only white space changes and than work from there. This is again not so important, but makes git blame and commits themselfs much less readable. Otherwise, yes, everything looks nice and clean, gg :)
Collaborator

ok

ok
lexonomy merged commit a07b35c6a8 into master 2 years ago manually
The pull request has been manually merged as a07b35c6a8.
Sign in to join this conversation.
No reviewers
No Label
No Milestone
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

This pull request currently doesn't have any dependencies.

Loading…
There is no content yet.