Open mhsdesign opened 1 year ago
We discussed here https://neos-project.slack.com/archives/C3MCBK6S2/p1694081919618779 that we want to rename the Neos WorkspaceName:
I'd favor renaming it to
NeosWorkspaceName
as it contains valid domain logic for Neos
I would like to deprecate the User
utility instead of renaming it to UserUtility
. The helper contained minimal logic, which is now mostly moved to NeosWorkspaceName
.
Removing or renaming the UserUtility
might be a little unwise, as its also used in the Neos.Demo!
See pr https://github.com/neos/neos-development-collection/pull/4530
I took the freedom to make this an issue of the DX epic (#4777)
Lately i was using the new ESCR WorkspaceFinder and passed at first the wrong
WorkspaceName
into it (because we have this thing twice in our code base)That got me thinking, if we have also other classNames that are duplicates and could lead to confusion. So i searched all duplicate base file names in this dev-collection and found the following. I excluded the results that i dont think are relevant.
Related: #4777
FusionView -> https://github.com/neos/neos-development-collection/issues/4476
its always hard to explain the difference in slack. And the fact that they have the same name doesnt make it easier. The Neos.Neos view should be named NodeFusionView or sth
Node ✅
lets rename the second (internal) one
-> https://github.com/neos/neos-development-collection/pull/4528
NodeAddress ✅
-> https://github.com/neos/neos-development-collection/pull/4540
User ✅
i would prefer, if the User utility has an Utility suffix We even only use it aliased as
UserUtility
-> https://github.com/neos/neos-development-collection/pull/4530
UserService
its confusing that we have this service twice
A comment from late 2015 suggest that
\Neos\Neos\Service\UserService
is "legacy", see commitNodeAggregateIds
why? Lets check if we can just use the shared model of the core
WorkspaceName ✅
why? Is the Neos.Neos WorkspaceName legacy? Can it be removed?
-> https://github.com/neos/neos-development-collection/pull/4534
CrCommandController and WorkspaceCommandController
why are those command controllers separated? Shouldn't they belong to one controller?
Exception
those exceptions should have more distinct names