Skip to content

How is it handled when other plugins also use Twig? #283

@arnowelzel

Description

@arnowelzel

I understand the motivation to create an object oriented approach for WordPress including Twig.

However, having an autoloader in a plugin or theme seems to be a bad idea, since there is only a global use statement which can not specify which autoloader to use for a specific namespace. So if any other plugin also uses Twig, it can happen that either the other plugin will load the wrong version of Twig or Clarkson-Core will get an outdated version provided by the other plugin.

How is this possible conflict handled?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions