-
Notifications
You must be signed in to change notification settings - Fork 17
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
Renaming work #130
base: develop
Are you sure you want to change the base?
Renaming work #130
Conversation
ok, I see now that it was worded as:
It wasn't clear that anything else was changing, need to think about this one. |
Yeah I'd like to figure out long term to fully rename without causing breaking changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good with it. Would like a spot check from @itdependsnetworks as well.
Starting to feel like this will cause a lot of confusion if we don't do the project rename and the package rename at the same time. Gets confusing when reviewing the GC project rename and starting to keep straight the project names, the plugin_config section and what that should be named etc. |
Yea, I am not sure about this, I think we need to change everything and have a proper rollout plan if we are going to go to this. |
In talking with Jeff, will certainly have to think about this, so please remove this from the Jan 9th deadline. One potential migration plan would be
This may allow us to support both app and plugin names for the time being. |
Unfortunately I don't think the symlink would work due to import for the config has the match the |
Good point... will have to think about that. |
No description provided.