You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One contributing factor may be that an inflectional class is shown both for the entry head-word as well as the inflected word-form (when these are distinct), cf.
In the production server, the inflectional class is only shown for the entry, not the inflected word form (for good reasons). See:
I don't see all the required information in the API. The Plain English and Linguistic categories are present, but not Nêhiyawêwin. Does this info need to be implemented into the API via the backend?
The inflectional class will no longer be shown in the outer search section, that is no big deal to implement.
What is shown is not the inflectional class (or its relabeling), but rather that of
V
andAI
, which is wrong. cf.What should be shown here is the relabeling of the single string
VAI-1
, for which the relabelings are:This is how it works in the production version:
This may be due to an incorrect implementation in the backend.
The text was updated successfully, but these errors were encountered: