Cascading meta to a sub-tree of routes
Maintainers usually reply within 1 day
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
- Domain
- web-dev
Research direction
Start by reviewing how +meta.json is currently associated with each +page.marko and how route subtrees are resolved. Define the cascade, overriding, and augmenting behavior for a shared meta file, with completion marked by documented behavior and tests covering inheritance and overrides.
Written by the indexing model from the issue text.
Description
Currently meta files +meta.json needs to exist per +page.marko. We can't cascade the same meta file for an entire sub-tree of routes at once. Such a capability could be quite useful to set default meta, and only overriding/augmenting where it makes sense. Perhaps something like https://www.11ty.dev/docs/data-cascade/
Can we have such a feature?
- Dominant language
- TypeScript
- Stars
- 175
- Forks
- 17
- Avg merge
- 13h 34m
- Merged PRs (30d)
- 16
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from marko-js/run
-
DEP0190: spawnServer passes args array with shell:true, triggering Node v26 deprecation warningOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Dev server answers 404 to every route after Vite restarts (e.g. after an edit of `vite.config.ts`)May be free again A pull request for this issue was closed without being merged. Open
Difficulty 4/5 1-2 days Newbie friendliness 15/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
marko-js/run#296 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
Similar issues
-
ready
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
wheresrhys/totf#1214 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
CodeChefVIT/ffcs#281 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
endora-commerce/endora-commerce#451 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
vetro-protocol/vetro-monorepo#1007 ·
Maintainers usually reply within 1 day