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: port read to typescript #816

Closed

Conversation

kenn-chen
Copy link

Description

Part of #659

Motivation and Context

Ported read to typescript as part of #659

How Has This Been Tested?

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@@ -12,5 +12,6 @@
{ "path": "@commitlint/resolve-extends" },
{ "path": "@commitlint/to-lines" },
{ "path": "@commitlint/top-level" },
{ "path": "@commitlint/read" }
Copy link
Author

Choose a reason for hiding this comment

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

Because read depends on top-level, I put the path of read under that of top-level here. Otherwise, the build would fail. I cannot find a reference saying that the order matters, it would be great if anyone can tell me something more about this.

Copy link
Member

Choose a reason for hiding this comment

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

Yeah, this is the order here is equal to the order of compilation. If something depends on another thing, it needs to be listed after that package 😄 So you are correct!

@kenn-chen kenn-chen mentioned this pull request Oct 4, 2019
18 tasks
@marionebl
Copy link
Contributor

Closing in favor of #922

@marionebl marionebl closed this Feb 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants