Skip to content

Parameterized Subroute #1866

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

Draft
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

L0neGamer
Copy link
Contributor

@L0neGamer L0neGamer commented Mar 31, 2025

Before submitting your PR, check that you've:

After submitting your PR:

  • Update the Changelog.md file with a link to your PR
  • Check that CI passes (or if it fails, for reasons unrelated to your change, like CI timeouts)

Trying to solve #1865

@@ -76,7 +76,7 @@ instanceNamesFromOpts (MkRouteOpts eq shw rd) = prependIf eq ''Eq $ prependIf sh

-- | Generate the constructors of a route data type.
mkRouteCons :: [ResourceTree Type] -> Q ([Con], [Dec])
mkRouteCons = mkRouteConsOpts defaultOpts
mkRouteCons = mkRouteConsOpts defaultOpts [] []
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I would appreciate recommendations on what to do for this.

@L0neGamer L0neGamer force-pushed the parameterized-subroute branch from 252cfbe to 952db23 Compare March 31, 2025 11:21
@L0neGamer L0neGamer force-pushed the parameterized-subroute branch from 952db23 to 1e3260e Compare March 31, 2025 12:20
@L0neGamer
Copy link
Contributor Author

there are some really weird memcpy errors in CI which I doubt are my fault.

@L0neGamer
Copy link
Contributor Author

ah, looks like the old TH operators take slightly more different parameters to what I expected. I can't fix this right now.

@L0neGamer L0neGamer marked this pull request as draft April 2, 2025 08:33
@jezen
Copy link
Member

jezen commented Apr 2, 2025

Yeah I re-ran the failing builds because it didn't look like the failures were related to your change. Seemed to just be some transient Stack error.

Ok, we can save this change for a rainy day. It's at least clear what problem we're solving here 🙂

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