Skip to content

feat(create): Keep pluginsData key from template's package.json #3406

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

Merged
merged 1 commit into from
Mar 1, 2018

Conversation

rosen-vladimirov
Copy link
Contributor

In case project template has a preconfigured plugins data (for example API keys), it will be stored in the template's package.json.
After creating the project, CLI removes all keys except the one defined in PackageJsonKeysToKeep array from app/package.json file.
So it removes the predefined configuration of the pluginData.
Fix this by adding the entry "pluginsData" in the array, so we'll keep it as well.

In case project template has a preconfigured plugins data (for example API keys), it will be stored in the template's package.json.
After creating the project, CLI removes all keys except the one defined in `PackageJsonKeysToKeep` array from `app/package.json` file.
So it removes the predefined configuration of the pluginData.
Fix this by adding the entry "pluginsData" in the array, so we'll keep it as well.
Copy link
Contributor

@Mitko-Kerezov Mitko-Kerezov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@rosen-vladimirov rosen-vladimirov merged commit a6a0f5d into release Mar 1, 2018
@rosen-vladimirov rosen-vladimirov deleted the vladimirov/plugins-data branch March 1, 2018 11:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants