The asciidoc documentation states that the logger will receive objects
with a given interface, but sometimes we receive simple strings that
crash the documented code.
This is an automatic update of the package + a fix for a type error that
is detected with the newer typescript compiler.
I did this hoping to address the Dependabot concerns, but the update
didn't go far enough.
The type fix changes the type or error in `useFetch` from "unknown" to a
boolean (has error / no error), which is how we use it as far as I can
tell.
For some rules, rule-specific metadata.json overridden the `sqKey` for
all languages, so when the predeployment script collected all keys, it
did not list the actual, most canonical key "S****".
This leads to the incorrect display of coverage information on a rule
page that relies on the `allKeys` precomputed property to retrieve the
version of the analyzer that implements the rule.
The fix includes the generic rule metadata.json file into the aggregator
that computes `allKeys`, thus propagating it to every language-specific
metadata.
When an include is not surrounded by empty lines, its content is inlined
on the same line as the adjacent content. That can lead to broken tags
and other display issues.
This PR fixes all such includes and introduces a validation step that
forbids introducing the same problem again.
Triggered by the deployment failure that was caused by an invisible Unicode character in a rule's metadata.json.
This PR implements three conceptual changes:
- make the deployment parse error more informative
- prohibit the use of non-ASCII characters in the metadata.json files
- remove the existing non-ASCII characters from the existing rules
* Generate description and metadata for rules with no language, so that they get indexed.
* Index rules with different types in language specializations.
* Improve validation to reject new rules with no language specialization (i.e. only a predefined set of such rules is allowed because they were imported from Jira and kept for historical purposes).
* Write smaller JSON files, reduce their size by 30%.
* Improve test coverage of CLI application.
The broken UI test on master is the result of a temporal relaxation of the policy of "merge only PRs that are up-to-date with master": a snapshot-based test was introduced in one PR (#709) and was passing, and a UI change was introduced in another PR(#715) that changed the snapshot (but was not covered by the test at the time the second PR diverged from master)
Fix the two warnings observed when testing the SearchPage component:
- Each child in an array should have a unique "key" prop.
-> add a key prop to list items
- <div> cannot be nested in <p> (or sth to that effect)
-> change the relevant Typography components from "p" to "div"
Two warnings descovered when trying to test RulePage component:
- `<div>` nested in `<p>`
- `<Tabs>` component with contradictory attributes: `centered` and `scrollable`
