Michael Voříšek
Michael Voříšek
Thanks for the repro code. I will repro on my side and double check the exception. Aggregated fields should never be allowed to set in the first place and maybe...
I still do not understand the repro steps fully. @mkrecek234 Please post here a simple model /w one aggregate field and simple use of it, which throws the exception.
Yes, a lot of work is done to detect such data mismatches. I am reopening, as when we read the data after save (insert/update), we can even assert all values...
The repro steps/issue is clear since your previous comment. The `Update failed, exactly 1 row was expected to be affected` exception was generated as you probably had some unstable value...
PR is done, `Build / PHPStan (8.0, highest)` CI error seems unrelated
@ondrejmirtes can you please review this PR?
> 1. This PR does too many unrelated changes I have separated the verbose logging to https://github.com/phpstan/extension-installer/pull/42, all other changes are related > 2. I'm not even sure that [composer.json's...
@ondrejmirtes can you please review?
yes, repos including some extra conf manually need to be updated (otherwise phpstan will throw for config included twice), but this PR unifies how the composer config behaves - like...
I am very confident this is a bug, as currently, exported phpstan config using `extra` section must be declared for the root project manually like: https://github.com/mvorisek/atk4-hintable-mirror/blob/1.7.2/phpstan.neon.dist#L3 But then when this...