cabal
cabal copied to clipboard
Add js-options field to cabal file to allow passing custom preprocessing options for js (#10721)
The PR fixes the issue (#10721) by adding a new js-options field to cabal file that are passed to componentJsGhcOptions.
Please advise on the testing strategy, if any. Thank you @hsyl20 for investigation and suggestion how to fix it.
Please let me know if this is an acceptable feature at all, if so I'm gonna add any needed doc changes / changelogs.
Can you please add some tests?
js-optionsused with oldcabal-specversionjs-optionsused with correctcabal-specversion
@mpickering: are you satisfied with the PR now?
Let me rebase in order to prod CI.
@mergify rebase
rebase
✅ Branch has been successfully rebased
Hah, it seems the whitespace check is failing.
Should this be closed after https://github.com/haskell/cabal/pull/10949 ?
@ulysses4ever I've taken a look at the PR, and if the tests pass then yes, it fixes the issue.
To summarize what we have now:
- The name
js-optionsis incorrect, since we don't pass any options forjshere. - It should be called
jsp-optionswith automatic addition of-optJSP. - It’s worth making a proposal in the CApiFFI style. (JavaScriptApiFFI)
We can start doing 1 and 2 already 👀