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

[DataEntryTable] A duplicate new entry that updates an existing entry doesn't add it to Recent/Existing Entries #1586

Closed
imnasnainaec opened this issue Feb 18, 2022 · 1 comment · Fixed by #1622
Assignees
Labels
bug Something isn't working component: DataEntry frontend Size: M Medium sized issue

Comments

@imnasnainaec
Copy link
Collaborator

Describe the bug

When a new entry is a duplicate of an existing entry, the semantic domain of the new entry is added to the existing entry instead of the new entry being created. However, when that happens, the updated existing entry should be added either to the Recent Entries above the New Entry row or the the side box of Existing Entries in the domain.

To Reproduce

  1. Go to project setting and switch Autocomplete to Off;
  2. Go to Data Entry;
  3. Select a domain (e.g., 1.1);
  4. Submit a new entry (e.g., vernacular "Donut" and gloss "Doughnut");
  5. Press "Exit" to return to the tree;
  6. Select a different domain (e.g., 1.2);
  7. Submit the same entry;
  8. Deal with the pop-up that tells you it was a duplicate.
  9. Observe that the entry is not visible (but if you click done, then click the same domain again, that entry should now be visible in Existing Entries)
@johnthagen
Copy link
Collaborator

This also happens when Notes are added when a duplicate vern/gloss are entered with a new Note:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working component: DataEntry frontend Size: M Medium sized issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants