Skip to content

"Content mapper file extension '.const.json' is a built-in extension and cannot be registered by a content mapper." error is misleadingΒ #64917

Open

Description

@DetachHead

πŸ”Ž Search Terms

is a built-in extension and cannot be registered by a content mapper

πŸ•— Version & Regression Information

7.1-beta

⏯ Playground Link

No response

πŸ’» Code

{
    "compilerOptions": {
        "resolveJsonModule": true
    },
    "contentMappers": [{ "package": "json-const-content-mapper", "extensions": [".const.json"] }]
}

πŸ™ Actual behavior

> tsc --runExternalCode
error TS18066: Content mapper file extension '.const.json' is a built-in extension and cannot be registered by a content mapper.

this error message implies that .const.json specifically is a built-in extension, when in reality it's just .json.

πŸ™‚ Expected behavior

my preferred solution is that patterns like .const.json should be supported, to support content mappers like const-json-content-mapper

alternatively, the error message should be updated to clarify that .const.json isn't allowed because it conflicts with .json

Additional information about the issue

relevant issue: #32063

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Domain: Error MessagesThe issue relates to error messagingPossible ImprovementThe current behavior isn't wrong, but it's possible to see that it might be better in some cases

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions