You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be no valid reason to make that methods final and using final methods, this makes it impossible to a) overwrite these methods and b) mock them in tests (our problem at the moment).
To be honest, I don't find this kind of issue very constructive. The fact that you don't know the reason behind a developer's decision, does not mean that there is "no valid reason" for that decision or that said decision "makes no sense". Just as you probably wouldn't be happy about being told that mocking a state representation of a 3rd party package such as the Table class makes no sense and that there's no valid reason to create such a mock.
Feature Request
What
There are only two methods in the Table schema class which are marked as final, which seems to make no sense:
dbal/src/Schema/Table.php
Lines 274 to 283 in afcd624
Why
There seems to be no valid reason to make that methods final and using final methods, this makes it impossible to a) overwrite these methods and b) mock them in tests (our problem at the moment).
How
Just remove the "final" method modifier here:
dbal/src/Schema/Table.php
Lines 274 to 283 in afcd624
The text was updated successfully, but these errors were encountered: