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.

Sign up for GitHub

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

Jump to bottom

Date Issues: Stay at code, handle migel & al children for non active codes #17

Open
jbessi opened this issue Aug 5, 2022 · 1 comment
Open

Date Issues: Stay at code, handle migel & al children for non active codes #17

jbessi opened this issue Aug 5, 2022 · 1 comment
Assignees
@jbessi

Comments

@jbessi
Copy link
Contributor

jbessi commented Aug 5, 2022 •
edited
Loading

  • Stay at code: If changing version of a catalog or switching date, navigation to base code is triggered. Desired behavior could be if code exists in new version / date, stay at the codes page, otherwise move to base code.
  • handle migel & al children: If we choose a date and land at a code that was only active in the past, there can be problems with children. In the backend, we set children as active codes only but we do not have complete knowledge about validity of parents. See 17.30.01.d and change date to something before 01.10.2022. Then click on a child which leads to non existent record.
@jbessi jbessi self-assigned this Aug 5, 2022
@jbessi jbessi changed the title Stay at same code when changing version / date Date Issues: Stay at code, handle migel & al children for non active codes Nov 30, 2022
@jbessi
Copy link
Contributor Author

jbessi commented Dec 13, 2022 •
edited
Loading

Point two is solved in #26 transforming missing code error from backend to more meaningful message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jbessi jbessi

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jbessi