Currently the preset option in the API (-p or --preset in the CLI) is used for both Schema.org schemas (e.g. Article, NewsArticle) and for test suites that check for meta tags for sites like Twitter and Facebook.
It is worth considering at this early stage if it is worth splitting up these options and having a list of schemas specifically for JSON-LD/RDFa/Microdata and a list of presets that can do wider tasks, such as check meta tags and possibly inspect HTML markup too.
If presets should be renamed something else - e.g. "test suites" - or if a term like "test suites" should apply to any group of tests is also open for discussion.
It would likely be easier to refactor this now, before version 1.0, rather than later.
Currently the
preset
option in the API (-p
or--preset
in the CLI) is used for both Schema.org schemas (e.g.Article
,NewsArticle
) and for test suites that check for meta tags for sites likeTwitter
andFacebook
.It is worth considering at this early stage if it is worth splitting up these options and having a list of schemas specifically for JSON-LD/RDFa/Microdata and a list of presets that can do wider tasks, such as check meta tags and possibly inspect HTML markup too.
If presets should be renamed something else - e.g. "test suites" - or if a term like "test suites" should apply to any group of tests is also open for discussion.
It would likely be easier to refactor this now, before version 1.0, rather than later.