fix(linter): invalid tags in rule docs (#4646)

These are causing build errors in doc pages in PR #4640
This commit is contained in:
DonIsaac 2024-08-05 02:34:38 +00:00
parent b8e67538f8
commit b2da22b30f
2 changed files with 3 additions and 3 deletions

View file

@ -51,8 +51,8 @@ declare_oxc_lint!(
/// ///
/// ### Why is this bad? /// ### Why is this bad?
/// ///
/// Leaving the name off a function will cause <anonymous> to appear /// Leaving the name off a function will cause `<anonymous>` to appear
/// in stack traces of errorsthrown in it or any function called within it. /// in stack traces of errors thrown in it or any function called within it.
/// This makes it more difficult to find where an error is thrown. /// This makes it more difficult to find where an error is thrown.
/// If you provide the optional name for a function expression /// If you provide the optional name for a function expression
/// then you will get the name of the function expression in the stack trace. /// then you will get the name of the function expression in the stack trace.

View file

@ -41,7 +41,7 @@ struct AnchorIsValidConfig {
declare_oxc_lint!( declare_oxc_lint!(
/// ### What it does /// ### What it does
/// The HTML <a> element, with a valid href attribute, is formally defined as representing a **hyperlink**. /// The HTML `<a>` element, with a valid href attribute, is formally defined as representing a **hyperlink**.
/// That is, a link between one HTML document and another, or between one location inside an HTML document and another location inside the same document. /// That is, a link between one HTML document and another, or between one location inside an HTML document and another location inside the same document.
/// ///
/// While before it was possible to attach logic to an anchor element, with the advent of JSX libraries, /// While before it was possible to attach logic to an anchor element, with the advent of JSX libraries,