Skip to content

Conversation

cknitt
Copy link
Member

@cknitt cknitt commented Jul 29, 2025

No description provided.

@cknitt cknitt force-pushed the fix-error-message branch from c9e8b31 to 5366378 Compare July 29, 2025 08:04
Copy link

pkg-pr-new bot commented Jul 29, 2025

Open in StackBlitz

rescript

npm i https://pkg.pr.new/rescript-lang/rescript@7734 

@rescript/darwin-arm64

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/darwin-arm64@7734 

@rescript/darwin-x64

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/darwin-x64@7734 

@rescript/linux-arm64

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/linux-arm64@7734 

@rescript/linux-x64

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/linux-x64@7734 

@rescript/win32-x64

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/win32-x64@7734 

commit: 5366378

@cknitt cknitt requested a review from zth July 29, 2025 09:03
@zth
Copy link
Member

zth commented Jul 29, 2025

Could you add a test fixture for the error as well?

@cknitt
Copy link
Member Author

cknitt commented Jul 30, 2025

@zth Don't know how I can reproduce this error message (other than via #7738, but that's a different bug).

Maybe we can just merge as-is?

@zth
Copy link
Member

zth commented Jul 30, 2025

Well, it's important that we cover all our custom error messages with fixtures unless we absolutely can't. Not doing that is why this bug exists in the first place. But if it's very hard to reproduce then sure.

@cknitt
Copy link
Member Author

cknitt commented Jul 30, 2025

This is the fallback case if nothing else matches. I assume no test was added when it was implemented exactly because it is hard to reproduce.

@zth zth merged commit 12debe4 into master Jul 30, 2025
40 of 41 checks passed
@zth zth deleted the fix-error-message branch July 30, 2025 13:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants