Skip to content
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

refactor: move catalogs plugin to npm #6196

Merged
merged 9 commits into from
Apr 14, 2020

Conversation

kieckhafer
Copy link
Member

Resolves #6169

This PR removes the internal catalogs plugin, and installs the new api-plugin-catalogs from npm as a replacement.

The code in that npm plugin is the same, so the expected outcome of this PR is seeing nothing different than how the app currently runs.

Testing

Start reaction ,see that you can perform any catalog related mutations / queries.

Copy link
Contributor

@mpaktiti mpaktiti left a comment

Choose a reason for hiding this comment

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

Published changes to a product using the GraphQL API, the plugin works fine 🚢

@kieckhafer kieckhafer merged commit b2bd03f into trunk Apr 14, 2020
@kieckhafer kieckhafer deleted the refactor-kieckhafer-moveCatalogPlugin branch April 14, 2020 20:12
@kieckhafer kieckhafer mentioned this pull request Apr 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

move catalogs plugin to its own npm package, and install npm version Reaction
2 participants