remove "koku" from naming convention #161
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Wait, why!?
When we initially did this work, we named everything upstream as
koku
and then converted it all tocost-management
for downstream. That seems fine enough, but when it comes to converting the upstream to downstream for a release, it becomes really difficult and error prone to make sure all the appropriate name changes are made. This PR will eliminate the need for making the name changes when generating the downstream code. All we will need to do for downstream releases is make sure these are set correctly to:The next downstream release will also be difficult to implement all these name changes again, but once those are converted, we won't have to do it again.