Comment #⁨3⁩

All problems solved!

After commenting out Model::shouldBeStrict(); in my project, the lazyloading error dissapeared.

The control panel problem was actually an accidental space in the dutch translation file key. I filed a pull request for that and hope I did that the right way, as I'm taking my first steps in the contribution world.

  1. Answer
    Toby Toby Waterhole Founder May 9, 2024
    In reply to E Emmanuel Ingelaere

    Hi @Emmanuel Ingelaere, thanks for posting and working through this issue transparently, and sorry for any inconvenience it's caused in your production environment.

    While the bulk of Model::shouldBeStrict() issues were solved in v0.4.6, upon a little further digging, it looks like you uncovered a bug where a lazy loading error could still occur with some particular configurations of reactions - specifically, multiple reaction sets containing only a single reaction type. I've committed a fix for this which will be included in the next release.

    Thanks for your PR to fix the Dutch translation - a great first contribution! ⭐️