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
At this stage, when error occurs in synchronizer, it will be thrown (or rethrown) to consumer to catch it. There are places where we also throw our own (kind of) errors explicitly, for example:
`The '${repoId}' repository does not belong to any project in Monokle Cloud. Configure it on ${projectUrl}.`
);
In such cases, we should provide custom error codes and additional metadata if possible (e.g. user id, project id/name, related Monokle Cloud URL, etc). This will be very convenient for package consumers to be able to differentiate errors correctly and provide detail information (and possible actions/fixes) for such errors.
The text was updated successfully, but these errors were encountered:
At this stage, when error occurs in synchronizer, it will be thrown (or rethrown) to consumer to catch it. There are places where we also throw our own (kind of) errors explicitly, for example:
monokle-core/packages/synchronizer/src/utils/synchronizer.ts
Lines 109 to 111 in aa0afd9
In such cases, we should provide custom error codes and additional metadata if possible (e.g. user id, project id/name, related Monokle Cloud URL, etc). This will be very convenient for package consumers to be able to differentiate errors correctly and provide detail information (and possible actions/fixes) for such errors.
The text was updated successfully, but these errors were encountered: