-
Notifications
You must be signed in to change notification settings - Fork 701
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
Add js-options field to cabal file to allow passing custom preprocessing options for js (#10721) #10722
base: master
Are you sure you want to change the base?
Conversation
…ing options for js (haskell#10721)
Please let me know if this is an acceptable feature at all, if so I'm gonna add any needed doc changes / changelogs. |
@@ -621,6 +621,7 @@ buildInfoFieldGrammar = | |||
<*> monoidalFieldAla "cc-options" (alaList' NoCommaFSep Token') L.ccOptions | |||
<*> monoidalFieldAla "cxx-options" (alaList' NoCommaFSep Token') L.cxxOptions | |||
^^^ availableSince CabalSpecV2_2 [] | |||
<*> monoidalFieldAla "js-options" (alaList' NoCommaFSep Token') L.jsOptions |
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.
See above, needs to be guarded by availableSince
.
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.
I thought about it but got confused by a fact js-sources
are not guarded. Is it an omission?
Which value should I put here?
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.
@mpickering ? Should I add version 3.16?
Can you please add some tests?
|
The PR fixes the issue (#10721) by adding a new
js-options
field to cabal file that are passed tocomponentJsGhcOptions
.Please advise on the testing strategy, if any.
Thank you @hsyl20 for investigation and suggestion how to fix it.