Confirmed users
228
edits
MDN/Archives/Development/CompatibilityTables/Importer: Difference between revisions
Jump to navigation
Jump to search
MDN/Archives/Development/CompatibilityTables/Importer (view source)
Revision as of 08:42, 1 June 2015
, 1 June 2015Added a section to explain how to fix errors.
(→section_skipped: add link to spec table documentation on MDN) |
(Added a section to explain how to fix errors.) |
||
| Line 108: | Line 108: | ||
The first line (known as a "rule") says "Expect a <code>tr_open</code>, followed by optional whitespace, followed by a <code>spec_name</code>, ...", where the rules <code>tr_open</code> and <code>spec_name</code> elements are defined further down in the grammar. The PEG engine tries to match the MDN page against the grammar. If successful, the content defined by the elements can be extracted for further processing. If the grammar doesn't match, then the rule where matching stopped can be reported for a human to think about. | The first line (known as a "rule") says "Expect a <code>tr_open</code>, followed by optional whitespace, followed by a <code>spec_name</code>, ...", where the rules <code>tr_open</code> and <code>spec_name</code> elements are defined further down in the grammar. The PEG engine tries to match the MDN page against the grammar. If successful, the content defined by the elements can be extracted for further processing. If the grammar doesn't match, then the rule where matching stopped can be reported for a human to think about. | ||
=== When fixing an error === | |||
If you want to help fix these errors, the best place to find an error to fix is the [https://browsercompat.herokuapp.com/importer/issues importer issues page]. Click on the links to go to the Parse results page for each page that raised an issue. | |||
On these pages you will see a variety of data about each MDN page's compat data important status. The most useful items are "MDN URL", "Issues", and "Actions" > "Reset" button. | |||
You need to read the "Issues" information to find out what the problem is. Look up the issue code in "The Issues" section of this page, below, to find out how to tackle fixing the problem. | |||
Click on the link in the "MDN URL" section to go directly to the MDN page that has a problem, and edit the page to try to fix the problem. | |||
Next, click the "Reset" button to get the system to re-download and re-parse the MDN page. If you successfully fixed the problem, the "Issues" section should list a message of "None detected." If this isn't the case, repeat the process and try again. | |||
If you can't fix an error, contact the MDN writers about it using MDN's IRC channels or mailing lists. | |||
== The Issues == | == The Issues == | ||