Liquid class inheritance

[DBA]

Currently:

• Document is a Tag
• Block is a Tag
• If is a blog, so it is a tag

I find this to make less sense than

• Document is a Document and implements Block behaviors
• Block is not a Tag
• If is a Tag and implements Block behaviors

The current inheritance chain makes it hard to change document, and to some extent block, without affecting tag directly.

If this makes sense it's something that could be changed for liquid 3, effectively making it more modular and cleaner.

Best regards,
DBA

[phoet]

4 years ago... can we close this?

[arthurnn]

Closing this, as this is referring to a old version of liquid.. Please let us know if this is still a issue.

thanks