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

TS Check, Lint, and Format new-package/ and vendor/ #187

Merged
merged 5 commits into from
Jul 8, 2024

Conversation

lishaduck
Copy link
Contributor

@lishaduck lishaduck commented Jul 6, 2024

Part 1 of 2.

Relates: #125

@lishaduck
Copy link
Contributor Author

lishaduck commented Jul 6, 2024

FYI, test failures are outdated snapshots, not #189, although that warning is visible in the logs.

console.error(
`There are extraneous dependencies in the ${exampleConfiguration}/ configuration: ${remainingKeys}`
// prettier-ignore
Copy link
Owner

@jfmengels jfmengels Jul 7, 2024

Choose a reason for hiding this comment

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

I have to admit I'm not fond of having disable checks (for prettier or for TS) in files that package authors will then own.
Maybe in this case, we can create a new variable const keys = remainingKeys.join(', '); above console.error(...)?
That should get rid of the need for the ignore.

Copy link
Owner

Choose a reason for hiding this comment

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

You marked this as resolved, but the comment is still here. Did you apply it on a different branch maybe?

Copy link
Owner

Choose a reason for hiding this comment

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

Let's resolve this later, let's not block all the other PRs because of this.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Huh. Well, once it's all merged I can check again.

@jfmengels
Copy link
Owner

I'll merge this PR. We can always improve things later, I don't want you to fall into Git branch hell 😅
And thanks again for all this work, it's incredible! ❤️

@jfmengels jfmengels merged commit 7ca8d82 into jfmengels:main Jul 8, 2024
3 checks passed
@lishaduck
Copy link
Contributor Author

lishaduck commented Jul 8, 2024

I'll merge this PR. We can always improve things later, I don't want you to fall into Git branch hell 😅 And thanks again for all this work, it's incredible! ❤️

It's a bit too late for that 🤣 (it was worse, I rebased a few PRs and dropped some stashes):
Screenshot 2024-07-08 at 5 10 26 PM

I mean, that's what summer break is for, eh? Finding projects? Enjoying not having to tune out teachers while you edit this and that? 😉

@jfmengels
Copy link
Owner

Right, but if I waited a few more days, who knows how much worse it would have been 😄

@lishaduck
Copy link
Contributor Author

Right, but if I waited a few more days, who knows how much worse it would have been 😄

True, true... YIKES!

@lishaduck lishaduck deleted the ts-check branch July 8, 2024 22:41
@lishaduck lishaduck mentioned this pull request Aug 8, 2024
23 tasks
lishaduck added a commit to lishaduck/node-elm-review that referenced this pull request Nov 10, 2024
Addresses @jfmengels's feedback from jfmengels#187 (comment).

Co-authored-by: Jeroen Engels <jfm.engels@gmail.com>
@lishaduck lishaduck mentioned this pull request Nov 10, 2024
lishaduck added a commit to lishaduck/node-elm-review that referenced this pull request Nov 10, 2024
Addresses @jfmengels's feedback from jfmengels#187 (comment).

Co-authored-by: Jeroen Engels <jfm.engels@gmail.com>
lishaduck added a commit to lishaduck/node-elm-review that referenced this pull request Nov 10, 2024
Addresses @jfmengels's feedback from jfmengels#187 (comment).

Co-authored-by: Jeroen Engels <jfm.engels@gmail.com>
jfmengels added a commit that referenced this pull request Nov 10, 2024
Addresses @jfmengels's feedback from #187 (comment).

Co-authored-by: Jeroen Engels <jfm.engels@gmail.com>
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