-
Notifications
You must be signed in to change notification settings - Fork 29
[RFC] Reorganizing command names #60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
looks good to me. |
yes, you got them right. i wonder if we should leave out :workspace: from the commands that are about a workspace. in the end, all node commands are about workspaces as well, everything except node types is. having phpcr:purge, phpcr:import / export, phpcr:query would be more compact than the "workspace" in the middle. wdyt? |
Hmm, the problem I think is that we need the In addition I think wdyt? |
agreed on all points. i prefer a bit longer over inconsistent. |
i will tag things now as otherwise jackalope is not installable. but i will just cheat and update the tag on phcpr-utils after merging this PR... |
Updated .. have separated workspace:purge and node:remove - you cannot purge "/" from node:remove and you cannot purge a path from workspace:purge. I was intending to push some tests for all the commands too, but I had already been doing that for 2 hours and only have 2.5 tests done :) Might see if I can do functional tests instead - as such I havn't actually tested all these changes. |
very cool, thanks. and indeed good idea to separate purge and remove, avoids accidental data complete loss. i will change the remove path argument to be required and no default value after merging the PR. |
I guess the DoctrinePHPCRBundle needs updating now? |
yes |
This is just an proof of concept PR, so basically I propose to renmae the classes as follows:
and that would then translate to the following command schema:
Not sure if I have categorized things correctly, does
dump
,import|export
etc belong inworkspace
?