glsl-language-toolkit

glsl-language-toolkit copied to clipboard

This breaks code e.g. ```glsl // #define noise snoise #define noise cnoise //... noise(position) ``` Formatter would replace the define with `#define noise (cnoise)`, which would break the code `(cnoise)(position)`....

Lutymane

Allow more values for `#include <...>`

4

Value should allow path slashes `\`, `/`, different symbols `$@-` whitespaces. Actually just any characters. ```glsl #include #include #include ``` I tried to do this similar to `TOKEN.STRING`: ```ts TOKEN.MODULE...

Lutymane

I get the following error: ``` error printing {"kind":"ppExtension","extension":{"image":"GL_OES_standard_derivatives","startOffset":11,"endOffset error printing {"kind":"translationUnit","declarations":[{"kind":"ppExtension","extension":{"image":"GL_OES_standar [error] shader.frag: Error: unexpected n type ppExtension [error] {"kind":"ppExtension","extension":{"image":"GL_OES_standard_derivatives","startOffset":11,"endOffset ``` (unabriged, the print statements are simply cut off)...

jsangmeister

The formatter does not seem to have any extensions registered for compute shaders, so I have added a few that I think would commonly be used (I myself use .csh)

jbritain