A taxonomy's hierarchy
configuration value is dependent on content loaded into the system. Using a number of constants on VocabularyInterface
, the hierarchy value assists Taxonomy module in knowing whether to update after inserts/updates and in determining the proper help text to show when editing terms.
As this value is dynamically determined based on term content, which is not exported side-by-side to the vocabulary, and is thus mutable, it should not be exported to configuration where it may appear as updated when deploying config from different instances of a site (dev to prod, for example.)
I'm not an expert or maintainer of Taxonomy module, so not sure if this is more complicated than what I've described. It would, in its simplest form, be a one-line change to the annotation, but I'm betting it's not that simple.
Comments
Comment #12
pameeela CreditAttribution: pameeela commentedThere is no hierarchy value included in taxonomy export, I guess this has changed at some point since this report.
Here is an example config export for a Tags vocab with four nested levels in the hierarchy:
Comment #13
amateescu CreditAttribution: amateescu for Tag1 Consulting commentedThis was fixed in #2957381: Data model problems with Vocabulary hierarchy, so I'm going to mark it as a duplicate :)