Unverified Commit 4688cfe2 authored by Rahul Gaba's avatar Rahul Gaba Committed by GitHub

Update the text for eslint/no-page-custom-font rule (#25117)

## Documentation / Examples

- [x] Make sure the linting passes
parent 784c30cc
...@@ -46,7 +46,7 @@ module.exports = { ...@@ -46,7 +46,7 @@ module.exports = {
context.report({ context.report({
node, node,
message: message:
'Custom fonts should be added at the document level. See https://nextjs.org/docs/messages/no-page-custom-font.', 'Custom fonts not added at the document level will only load for a single page. This is discouraged. See https://nextjs.org/docs/messages/no-page-custom-font.',
}) })
} }
}, },
......
...@@ -66,7 +66,7 @@ ruleTester.run('no-page-custom-font', rule, { ...@@ -66,7 +66,7 @@ ruleTester.run('no-page-custom-font', rule, {
errors: [ errors: [
{ {
message: message:
'Custom fonts should be added at the document level. See https://nextjs.org/docs/messages/no-page-custom-font.', 'Custom fonts not added at the document level will only load for a single page. This is discouraged. See https://nextjs.org/docs/messages/no-page-custom-font.',
type: 'JSXOpeningElement', type: 'JSXOpeningElement',
}, },
], ],
...@@ -94,7 +94,7 @@ ruleTester.run('no-page-custom-font', rule, { ...@@ -94,7 +94,7 @@ ruleTester.run('no-page-custom-font', rule, {
errors: [ errors: [
{ {
message: message:
'Custom fonts should be added at the document level. See https://nextjs.org/docs/messages/no-page-custom-font.', 'Custom fonts not added at the document level will only load for a single page. This is discouraged. See https://nextjs.org/docs/messages/no-page-custom-font.',
type: 'JSXOpeningElement', type: 'JSXOpeningElement',
}, },
], ],
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment