You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that the content model constants are defined and organized in the ContentModel class, I don't think we need the equivalent constants on the Processor class anymore. We should either remove the constants on the Processor class or at least mark them as deprecated.
For example, the constant for the the compound content model is defined in these two places:
Processor.CONTENT_MODEL_COMPOUND
ContentModel.COMPOUND
I also think that ContentModel should be moved to the ast package.
The text was updated successfully, but these errors were encountered:
robertpanzer
added a commit
to robertpanzer/asciidoctorj
that referenced
this issue
Jul 25, 2016
Now that the content model constants are defined and organized in the ContentModel class, I don't think we need the equivalent constants on the Processor class anymore. We should either remove the constants on the Processor class or at least mark them as deprecated.
For example, the constant for the the compound content model is defined in these two places:
I also think that ContentModel should be moved to the ast package.
The text was updated successfully, but these errors were encountered: