Is there any appetite to support yesmeck/remix-routes?

Open
#22 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript

Research direction

Start by reading the route-generation flow in Remix-Forge and compare it with the remix-routes package's $path and SearchParams outputs. Define whether the project should invoke a route:build script, include SearchParams in generated route options, or both; done means the supported behavior and scope are agreed and covered by appropriate generation checks.

Written by the indexing model from the issue text.

Description

Background: remix-routes package codegens you a typesafe method $path that you can use for typesafe routing. In addition to this you can give your route typesafe search params by exporting a SearchParams type.

A couple of awesome things this could enable:

  1. trigger a route:build script directly from the SearchParams object in the route file.
  2. Add the the search params type to the list of options to generate for the route.
Dominant language
TypeScript
Stars
89
Forks
7
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from code-forge-io/Remix-Forge

All issues in code-forge-io/Remix-Forge

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.