refactor package data accessing, set up for per-package options transformer functions #55
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.
branched from #50, with some additional refactors (diff)
new approach for #10 after closing #47
currently only includes options transformation for class properties -- will add others here if this approach seems good to move forward with
changes:
getNewPackageName
andgetNewPackageOptionsTransformer
to be used instead of accessingpackageData
directly:getNewPackageName
returns that{ name: string, optionsTransformer: options -> options }
optionsTransformer
,getNewPackageOptionsTransformer
-- defaults to returning an identity functionConfigItem
class