mgechev / mgechev/angular-route-parser
Feature request
- Dominant language
- No language data
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Would I would love is the ability to read out the name option from every route that has one. (tbh, I have seen this name thing in samples, and I like it, but it doesn't seem part of the official API)
The other thing I want in the the data property, that way we can pull in additional data from the router into Scully.
If it's possible to read out an entire custom property, that would be even better, as that would enable me to do something like:
```ts
interface ScullyRoute extends Route {
ScullyData?: {
title?: string;
description?: string;
publish?: boolean;
};
}
const routes: ScullyRoute[] = [
{path: '', component: UserComponent},
{path: ':userId', component: UserComponent},
{
path: ':userId/:friendCode',
component: UserComponent,
ScullyData: {description: 'List user with his BFF'},
},
{
path: ':userId/:posts/:comments',
component: UserComponent,
ScullyData: {publish: false, title: 'Deep nesting sample'},
},
];
```
Contributor guide
No contributing guide indexed for this repository
Research direction
No source files, tests, or entry points are mentioned in the issue. First clarify whether route names, the data property, and arbitrary custom route properties are all required, then define the expected parsed output and tests before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100