SSWConsulting / SSWConsulting/SSW.Rules
✨ Related Rules - Update Related Rule URIs to Match Redirects
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 26
- Forks
- 17
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 2
Description
Requested by: @jakebayliss via YakShaver.ai 🦬
cc: @jakebayliss, @Marxoz, @PothieuG, @Freego1783
Hi Team!
🟥 Watch the video (1 min 41 sec)
Url from screen share: https://www.ssw.com.au/rules-beta/3-steps-to-a-pbi
Pain
Update the related rule URIs on the rule page to ensure they match the new redirects, ensuring users are directed to the correct related rules.
Acceptance Criteria
- Related rule URIs on the rule page should match the new redirect URIs.
- When a user clicks on a related rule, they should be redirected to the correct rule page.
- Ensure that all related rules are displayed correctly with the updated URIs.
Screenshot
Figure: Related rule URIs do not match due to redirects
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
Start from the rule page at /rules-beta/3-steps-to-a-pbi and inspect how its related rule URIs are defined and rendered. Compare each URI with the new redirect destinations, then verify that every related-rule link opens the intended rule page and all related rules display correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100