- 🇺🇸United States DamienMcKenna NH, USA
How much of this do we want to put into v3? 🌱 Plan for Schema Metatag 3.0.0 Fixed
I think we should consider this a legacy module that doesn't change significantly, and consider Schema.org Blueprints as the long-term successor.
Of course I wonder now if we should just move everything into this module in the interest of just having everything available in one location, but do a better job of splitting out the PropertyType plugins? E.g. why is HowToStep included in the main module?
- 🇺🇸United States wells Seattle, WA
I think we should consider this a legacy module that doesn't change significantly, and consider Schema.org Blueprints as the long-term successor.
I'm inclined to agree. I've gone from wanting to break this up to just having it be a monorepo.
I was prototyping some refactoring to make properties more reusable but got away from it a while back. I also had some decent success using an entity system hook instead of a bunch of class and submodules but, again, got away from that work. I'll try to find some time to dig back in to those WIP branches soon...
- 🇺🇸United States DamienMcKenna NH, USA
At this point I'm in favor of just adding everything to this module and encouraging people to use Schema Blueprints as a more flexible, more versatile solution.
- 🇺🇸United States wells Seattle, WA
Yeah. Unfortunately I got too far away from #19... I was trying to prototype a way to keep everything under one module but without having to group tags in to submodules. Parts of that are very confusing and it just feels a little silly to have e.g. 10+ classes that each represent the "@id" property exactly the same way.