We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Recommendations to start using the ddump-splices GHC option start showing up around here:
https://www.yesodweb.com/book/basics#basics_routing
But by this point, the learner only really knows how to run this command:
stack runghc helloworld.hs
A quick example of running GHC (via stack) with the "ddump-splices" against helloworld.hs would be great.
The text was updated successfully, but these errors were encountered:
Similarly, there's a suggestion to (similar to the ddump-slices option) build Haddock documentation to understand the generated code better.
An example of that for helloworld.hs would be great, too.
Sorry, something went wrong.
This may help you regarding ddump-splices: https://stackoverflow.com/questions/47702242/passing-ddump-splices-to-stack-script-interpreter
The answer to this related question I asked was helpful and relevant:
https://stackoverflow.com/questions/58343614/how-can-i-see-a-specific-files-generated-template-haskell-code-when-using-yesod
No branches or pull requests
Recommendations to start using the ddump-splices GHC option start showing up around here:
https://www.yesodweb.com/book/basics#basics_routing
But by this point, the learner only really knows how to run this command:
stack runghc helloworld.hs
A quick example of running GHC (via stack) with the "ddump-splices" against helloworld.hs would be great.
The text was updated successfully, but these errors were encountered: