tagName mapping options

[azu]

textlint-plugin-html/src/mapping.ts

Lines 3 to 23 in 08d7a6a

	export const tagNameToType = {
	"p": "Paragraph",
	"ul": "List",
	"ol": "List",
	"li": "ListItem",
	"q": "BlockQuote",
	"blockquote": "BlockQuote",
	"code": "CodeBlock",
	"hr": "horizontalRule",
	"br": "break",
	"em": "Emphasis",
	"strong": "Strong",
	"a": "Link",
	"img": "Image",
	"h1": "Header",
	"h2": "Header",
	"h3": "Header",
	"h4": "Header",
	"h5": "Header",
	"h6": "Header",
	} as const;

Currently, tagName mapping is hardcode.
However some use cases force change the mapping.

For example, a user want to treat div as p.
Of course, the user can create custom plugin.
But, it is easy to add new option than creat a fork.

{
   "plugins": {
       "html": {
           "tagNames": {
             // new mapping
             "div": "Paragraph"
           }
       }
   }
}

This option is a bit inflexible and we need to consider options that can satisfy a more varied set of use cases.

📝 textlintrc is JSON. So, we can not write JS Code as logics in option.