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

[0.10] - Add logging to migration actions #1379

Merged

Conversation

pileks
Copy link
Contributor

@pileks pileks commented Nov 1, 2022

This PR introduces the @polywrap/logging-js package which currently contains the types/interfaces required for packages other than the CLI to interact with logging.

This introduces one caveat - intlMsg currently only works on the CLI level.

I'd like to open some discussion as to how we'd want to handle intl in the case where we really do go forward with logging being used in multiple packages.

@@ -46,8 +46,11 @@ export function deserializePolywrapWorkflow(
);

if (versionCompare === -1) {
// Warn user to migrate their manifest
options?.logger?.warn(`PolywrapWorkflow is using an older version of the manifest format (${anyPolywrapWorkflow.format}). Please update your manifest to the latest version (${latestPolywrapWorkflowFormat}) by using the "polywrap manifest migrate <type>" command.`);
Copy link
Contributor

Choose a reason for hiding this comment

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

This looks fine to me, but just want to call out that we're making an explicit reference here to the Polywrap CLI, which is an external dependency to this package.

@dOrgJelli dOrgJelli merged commit 2632172 into origin-0.10-dev Nov 2, 2022
@dOrgJelli dOrgJelli deleted the pileks/patch-0.10/add-migration-warnings branch April 10, 2023 17:02
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.

2 participants