-
Notifications
You must be signed in to change notification settings - Fork 23
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
chore: use reverse dependency tree in oao publish #102
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This can be very useful, thanks! Please check my comment; otherwise I think it's good to go!
src/__tests__/publish.test.js
Outdated
try { | ||
await publish(merge(NOMINAL_OPTIONS)); | ||
} catch (err) { | ||
throw new Error('SHOULD_NOT_HAVE_THROWN'); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the purpose of this try-catch block? If the publish()
fails, the test will already fail…
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok I'll remove it
@guigrpa pls re-review. Since we're doing |
Hmmm, what would be the added value of the "alphabetical" publishing? If it's not evident, I would remove the flag entirely. |
@guigrpa updated PR, please review :) |
Good to go, thanks! |
closes #101
This would allow users to run
oao publish --tree
so the leaves of a dependency tree get published first