Files
eslint/messages/config-serialize-function.js
Josh Goldberg ✨andGitHub 36a353c719 chore: formatted files with Prettier via trunk fmt (#19355)
* chore: remove formatting-related lint rules internally

* chore: formatted files with Prettier via trunk fmt

* rm .prettierrc.json

* chore: correct comment directives and formatting

* Apply introduced fmt changes post-merge

* Also disable MD010 and MD030 in preparation for 19355

* Also disable MD013 in preparation for 19355

* Updated tools/update-rule-type-headers.js to print tabs

* Fix introduced issues from the main merge

* Manually format conf/*.json

* Switch conf/*.json files back to two spaces, per prettier config

* chore: empty commit to hopefully unblock GitHub
2025-03-19 11:18:08 -04:00

31 lines
942 B
JavaScript

"use strict";
module.exports = function ({ key, objectKey }) {
// special case for parsers
const isParser =
objectKey === "parser" && (key === "parse" || key === "parseForESLint");
const parserMessage = `
This typically happens when you're using a custom parser that does not
provide a "meta" property, which is how ESLint determines the serialized
representation. Please open an issue with the maintainer of the custom parser
and share this link:
https://eslint.org/docs/latest/extend/custom-parsers#meta-data-in-custom-parsers
`.trim();
return `
The requested operation requires ESLint to serialize configuration data,
but the configuration key "${objectKey}.${key}" contains a function value,
which cannot be serialized.
${
isParser
? parserMessage
: "Please double-check your configuration for errors."
}
If you still have problems, please stop by https://eslint.org/chat/help to chat
with the team.
`.trimStart();
};