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

bug: Clearing lexeme fields leads to exception notice #1742

Open
laineyhm opened this issue Mar 24, 2023 · 0 comments
Open

bug: Clearing lexeme fields leads to exception notice #1742

laineyhm opened this issue Mar 24, 2023 · 0 comments
Labels
bug An existing problem with our app in production user observed Issue reported by a user with our app in production

Comments

@laineyhm
Copy link
Collaborator

Describe the bug
When you take out the lexeme forms from a project that was imported through LIFT, you get the following notice:

Screenshot (78)

even though when you click out of the notice, you can go on as usual.

To Reproduce
Steps to reproduce the behavior:

  1. In FLEx, make a project, can have as few as 2 entries. Fill in the lexeme form and the gloss and/or definition in the sense for these entries.
  2. Export the project as a LIFT file of the Full Lexicon.
  3. In Language Forge, create a new non-send receive project. Name it and then import entries from LIFT file.
  4. In the Language Forge editor, delete the entries to the "word" fields.
  5. After a moment, you will receive the exception notice.
  6. Click out of the exception notice, and observe that you can edit as normal.

Expected behavior
Although L:IFT imports are not a recommended way to go anymore, the expected behavior in this scenario is to be able to remove the data in word fields without a problem or a notice of a problem. In a project that's created in Language Forge or created through send/receive, this exception does not occur.

Additional context
This issue was reported by Ken Zook on March 14, 2023.

@laineyhm laineyhm added bug An existing problem with our app in production user observed Issue reported by a user with our app in production labels Mar 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An existing problem with our app in production user observed Issue reported by a user with our app in production
Projects
Development

No branches or pull requests

1 participant