Open mhsdesign opened 1 year ago
For example the code says here
"CREATE METHODS FÜR ALLE COMMANDS"
should we do this actually?
-> solved via https://github.com/neos/neos-development-collection/pull/4489 ✅
@pKallert noted that we match unused methods
Unneeded permissions from deprecated methods: Is there a way to do an automated check? Old permissions @Paula Kallert
cleanup todos. There were many todo comments added from 8.3 to 9.0. Some of those are probably already resolved and were just early thoughts but i saw here and there a few that probably need to be addressed. Either way we should reduce the todos - especially if they are outdated.
cleanup dangerous
assert
expressions. Instead of using php docs var tag/** @var
we started using phpsassert
. But we should make sure that we never assert anything that could possibly really fail, as for this cases we should throw a real exception.cleanup commented code. Some implementations are partially commented out as they havent been adjusted to work with Neos 9.0 yet and to avoid linting errors. We should make sure we know about all places and fix them or remove them.
cleanup commented/skipped tests. We started to write tests in behat. The old Neos.Neos functional tests (also regarding fusion prototypes) should be migrated to behat. Not necessarily 1 to 1 but to cover all important features / usecases.
cleanup unused new code
NodeVariationInternals
check php inline docs. References via
{@see fooo}
should link to existent places. I just found out that our main read model - the beloved node - had long unnoticed misleading documentation, because the docs were originally written for methods and not properties. (Maybe leverage phpstan to check@see
annotations?cleanup dead doc generation
cleanup dead policy yaml regex
cleanup dead imports https://github.com/neos/neos-development-collection/pull/4747
everything around
NodeReferenceSnapshot
is marked wip and todo? So does copying nodes work if they have references? https://github.com/neos/neos-development-collection/blob/0fe7b5ac74ccb74822512cd04cafb0e310d958cd/Neos.ContentRepository.Core/Classes/Feature/NodeDuplication/Dto/NodeReferenceSnapshot.php#L21todos that are not marked as todo but just via
?
and a newline\n
like https://github.com/neos/neos-development-collection/blob/3a7aa79e857e9d78e4c0ade1017dee643335f09d/Neos.ContentRepository.Core/Classes/Projection/ContentGraph/VisibilityConstraints.php#L20check for
Todo
string in exception messages and enhance details or create a dedicated exception subclass.unify license headers https://github.com/neos/neos-development-collection/issues/5138
Change workspace seems untested https://github.com/neos/neos-development-collection/pull/5184#issuecomment-2252330504