SSWConsulting / SSWConsulting/SSW.Rules

Table formatting is different when published and looks bad

Open
#522 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
26
Forks
17
Avg merge
14h 39m
Merged PRs (30d)
2

Description

The features column in the table on this rule looks bad when published, however, looks good when editing on GitHub.

  1. Please investigate and fix

image
Figure: Bad example - when published to the Rules website

image
Figure: Good Example - when editing on GitHub

AB#61561

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked rule and compare its table as rendered on GitHub with the published Rules website. Trace the TypeScript/Next.js publishing path; no file or test is named in the issue, so done means the features column renders consistently and no longer looks bad when published.

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
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.