rstackjs / rstackjs/path-serializer
Relative paths are not transformed
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 8
- Forks
- 4
- Avg merge
- 9h 54m
- Merged PRs (30d)
- 3
Description
@@ -25,71 +25,71 @@
{
"column": 1,
"endColumn": 33,
"endLine": 17,
"line": 17,
- "message": "Cannot find file `../../getting-started/next`",
+ "message": "Cannot find file `..\..\getting-started\next`",
"nodeType": "Program",
"ruleId": "remark-validate-links:missing-file-missing-file",
"severity": 1,
},
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 by reproducing the snapshot discrepancy shown in the issue, focusing on how relative paths are serialized. Trace the path-serialization entry point and identify where relative paths retain forward slashes. Done means the reported message uses the expected relative-path separators consistently and the relevant snapshot output passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing-qa, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100