LuteOrg
QOL: Auto save child changes when clicking into parent -- blocked by #99
Is your feature request related to a problem? Please describe.
It's very annoying to update a parent word via a child. You need to click the child, make changes, save. Click the child, click the parent, make changes, and then save.
Describe the solution you'd like
It'd be really nice if, when clicking on a parent, it would just auto save any changes to the child so that it would be quicker and easier (and the annoying dialogue wouldn't pop up).
When you click a parent word, it treats it like you saved first.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
This feature would be less needed if children were "more connected" to the parent (they didn't have their own definitions, they matched learning level, etc).
Yes, it is annoying -- when I've been editing the parent, I usually just go to the parent and don't worry about the child. Auto-save should be possible though -- I don't know if there are any issues with that.
Re matching learning level, there's an issue for that, #66, which I'd like to do soon, as I think it would be very useful.
Blocked by #99 as all terms should be created beforehand while reading a page - clarifies entity lifecycle.
Fixed in the develop branch. On term form:
Now when a parent tag is clicked when you're on the term form (if term was edited):
the reading pane updates as usual, and the form then shows the parent term.