mdn / mdn/rari

No way (flaws or build log) to detect errors in {{CSSInfo}}

Open
#161 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement idle
Dominant language
Rust
Stars
57
Forks
47
Avg merge
1d 11h
Merged PRs (30d)
68

Description

Summary

The macro {{CSSInfo}} uses mdn/data to display its content.

When there is no matching entre in mdn/data, the macro generate a text in red as error:
Capture d’écran 2023-03-17 à 07 52 20

This is good, but not enough: we detect such error only by visiting the page.

We need a way to detect all pages in error. For similar problems, errors are displayed in one of the two following ways:

  • As a flaw (this is the case when the {{Compat}} macro doesn't find the info)
  • In the build error log (this is the case when a Prism language tag is not supported).

Both cases allow us to find, track and fix these problems (I have no strong feelings)

URL

http://developer.mozilla.org/en-US/docs/Web/CSS/font-palette

Reproduction steps
  1. Go to http://developer.mozilla.org/en-US/docs/Web/CSS/font-palette
  2. There is the red message but nothing in the build log or in the flaws
Expected behavior

An error in the flaw list OR in the build log (no strong feeling about which one is the best!)

Actual behavior

No error outside the page itself

Device

Desktop

Browser

Chrome

Browser version

Stable

Operating system

Android

Screenshot

No response

Anything else?

No response

Validations

Contributor guide

Open the contributing guide

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 at the {{CSSInfo}} macro and the Rari build and error-reporting path, reproducing the missing mdn/data entry at the linked font-palette page. Done means the missing entry is reported outside the rendered page, either in the flaw list or in the build error log.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.