SSWConsulting / SSWConsulting/SSW.Rules
BUG - Next button not showing
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 26
- Forks
- 17
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 2
Description
cc: @UlyssesMaclaren
Hi @pierssinclairssw,
When you navigate directly to a rule URL e.g. https://www.ssw.com.au/rules/management-is-your-client-clear-on-how-you-manage-projects the 'next' and 'previous' buttons dont show up.
This is beacuse the buttons navigate through a category, and some rules have multiple categories so you need to navigate to the rule from a category for the buttons to show up.
- Add ApplicationInsights to the 'next' and 'previous' buttons
- See if these buttons are used. If they are, action the next 2 items:
- When a rule is opened in a new tab, it should remember which category it come from.
- When you dont navigate through a category it should show the 'next' and 'previous' buttons. Our current thinking to resolve this is to default to the first category
Thanks,
-Brady
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Use the linked rule URL as the reproduction entry point, then compare direct navigation with opening the rule from a category. Trace how category context controls the next and previous buttons; done means those buttons appear in both paths, preserve the originating category in a new tab, and have Application Insights tracking if they are used.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100