You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Did you search the issue queue for existing issue? Search issues
Issue Description
We're replacing all Meteor.Error calls with the ReactionError, currently the ReactionError class is deeply nested inside /imports/plugins/core/graphql/server/no-meteor/ directories. Should the ReactionError class be ported into it's own npm package?
Possible Solution
Move ReactionError class into an npm package import ReactionError from "@reactioncommerce/reactionerror"
Versions
1.14
The text was updated successfully, but these errors were encountered:
Prerequisites
Issue Description
We're replacing all
Meteor.Error
calls with theReactionError
, currently the ReactionError class is deeply nested inside/imports/plugins/core/graphql/server/no-meteor/
directories. Should the ReactionError class be ported into it's own npm package?Possible Solution
Move ReactionError class into an npm package
import ReactionError from "@reactioncommerce/reactionerror"
Versions
1.14
The text was updated successfully, but these errors were encountered: