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

New MashStep doesn't get saved properly #628

Closed
matty0ung opened this issue Dec 6, 2021 · 3 comments
Closed

New MashStep doesn't get saved properly #628

matty0ung opened this issue Dec 6, 2021 · 3 comments

Comments

@matty0ung
Copy link
Contributor

matty0ung commented Dec 6, 2021

Adding a new mash step to an existing recipe, the mash step gets stored in the database but not associated with the mash, so it's disappeared next time you run the program. Culprit is NamedMashEditor::addMashStep() which is directly calling ObjectStoreWrapper::insert() instead of Mash::addMashStep(), plus, MashStep::setMashId() doesn't use the same boilerplate as all the other setters, which means it's not calling down to the ObjectStore/DB layer.

Working on a fix.

@matty0ung
Copy link
Contributor Author

Have made some progress. Code is no longer crashing but still two problems on recipe import from XML:

  • MashStep step numbers are not getting set
  • Mash / MashSteps are not showing up in the UI until you restart Brewtarget

Will continue investigating!

@matty0ung
Copy link
Contributor Author

Nearly there. Just have the MashSteps coming in backwards, which I know how to fix...

@mattiasmaahl
Copy link
Collaborator

Merged, closing.

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

No branches or pull requests

2 participants