Themosis Framework: loader paths

[cknott]

I am using twiggy in neovim and am very pleased with the overall features and experience.

However i was wondering if its possible to somehow point the "Go to definition" action for a template in a custom namespace (eg. @atoms/template/template.twig) to the correct path in the filesystem?

Thanks a lot
Christian

[moetelo]

Hello!

If you're using Symfony, it should gather custom namespaces by running the debug:twig command.

twiggy/packages/language-server/src/twigEnvironment/SymfonyTwigEnvironment.ts

Lines 50 to 58 in 1e9acae

	async #loadEnvironment(): Promise<TwigEnvironment | null> {
	const result = await this.#runSymfonyCommand<SymfonyTwigDebugJsonOutput>('debug:twig');
	if (!result) {
	return null;
	}
	return parseDebugTwigOutput(result);
	}

If not, let me know which framework you’re using

[cknott]

Thanks, im using the Themosis Framework which incorporates a Laravel environment to a Wordpress installation. Would it be possible to create a custom configuration / FrameworkEnvironment for this use case?

[moetelo]

Is there a way to programmatically resolve namespaces? For example, Symfony provides a CLI tool which has an option to query all the info about the current environment:

$ php bin/console debug:twig --format json

{
    ...
    "loader_paths": {
        ...
        "@Twig": [
            "templates\/bundles\/TwigBundle"
        ],
        "@!Twig": [
            "templates\/bundles\/TwigBundle"
        ],
        "(None)": [
            "templates"
        ]
    }
}

Or maybe the overall file structure is predefined?

---

Otherwise, we'll have to add an option to manually pass loader paths to the extension. This would also cover the cases like #2