It would be nice if the development environment included an automated test for when there are redundant explicit property assignments in the database. I'd imagine the implementation could look something like: for each explicit entry in the database, remove it and the deduced property assignments; run the deduction process; and determine whether the removed entry appears as deduced. (And then restore the previous state for the next entry.) Of course, that's if the deduction is done directly on the database; if it's done on an internal object, then that of course could be preferable.
If it turns out that running that test would be significantly expensive, then it could be part of a target named something like db:expensive-tests which we'd want to run before merging a PR.
It would be nice if the development environment included an automated test for when there are redundant explicit property assignments in the database. I'd imagine the implementation could look something like: for each explicit entry in the database, remove it and the deduced property assignments; run the deduction process; and determine whether the removed entry appears as deduced. (And then restore the previous state for the next entry.) Of course, that's if the deduction is done directly on the database; if it's done on an internal object, then that of course could be preferable.
If it turns out that running that test would be significantly expensive, then it could be part of a target named something like db:expensive-tests which we'd want to run before merging a PR.