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

Switching to analysis language with no spell-check dictionary doesn't disable suggestions #3183

Open
imnasnainaec opened this issue Jun 27, 2024 · 0 comments · May be fixed by #3185
Open

Switching to analysis language with no spell-check dictionary doesn't disable suggestions #3183

imnasnainaec opened this issue Jun 27, 2024 · 0 comments · May be fixed by #3185
Assignees

Comments

@imnasnainaec
Copy link
Collaborator

Describe the bug

If the top analysis language in a project is one without a spell-check dictionary, then no gloss spelling suggestions are loaded in data entry. However, if you use data entry first with a language that has a dictionary (e.g., "en") and then with one that doesn't (e.g., "tpi"), the loaded suggestions from the first persist for the second even though they are no longer relevant.

To Reproduce

Steps to reproduce the behavior:

  1. Go to project settings > Languages > Analysis
  2. Set "tpi" as the top analaysis language
  3. Go to Data Entry and enter any semantic domain
  4. Start typing in a Glosses field and no spelling suggestions should be offered
  5. Go to project settings > Languages > Analysis
  6. Set "en" as the top analaysis language
  7. Go to Data Entry and enter any semantic domain
  8. Start typing in a Glosses field and see that spelling suggestions are offered
  9. Go to project settings > Languages > Analysis
  10. Set "tpi" as the top analaysis language
  11. Go to Data Entry and enter any semantic domain
  12. Start typing in a Glosses field and see spelling suggestions, even though there shouldn't be any

Expected behavior

In step 12 above, no spelling suggestions should be offered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant