JetBrains.ReSharper.Plugins.Unity.Shaders

There a confusion between GetName which is for command name and a name assigned to entity defined with command. I.e. for Shader "Foo" Shader is a name and Foo is an entity name.

Push interface down by hierarchy. Can't just make it abstract, because generator doesn't support overriding of existing methods.

Parse the (filtered) pre-processor tokens

Pre-processor tokens can occur anywhere, which makes it harder to parse the rest of the file. So, like whitespace and comments, pre-processor tokens are marked as filtered, and don't get seen by the parser. However, we need to combine some of the tokens, (such as PP_WARNING and PP_MESSAGE) into elements. This pre-processor will loop over the original (not filtered) lexer and create and store the elements. They don't get inserted into the tree at this point, but are used by the missing tokens inserter. Note that the C# parser/preprocessor is a little more complex. The pre-processor tokens aren't filtered, and can actually contain comments and whitespace. So the C# pre-processor will run on the filtering lexer, and create and collect pre-processor elements. The missing tokens inserter has to be run on the newly created pre-processor elements to reinsert any comments. The collection of pre-processor elements are then fed back into the filtering lexer, so now the parser uses a lexer that removes whitespace, newlines, comments and pre-processor tokens, and the final missing tokens inserter will reinsert the created pre-processor elements.

Sub-class of keyword token types for ShaderLab command keywords.

Sub-class of keyword token types for ShaderLab command keywords.

Sub-class of keyword token types for ShaderLab block command keywords.

Sub-class of keyword token types for ShaderLab block command keywords.

Returns table of all shaders declared with ShaderLab + built-in shaders.

Alexander.Bondarev: todo: it only defines default properties for ShaderLab files, actual properties provided in . todo: it isn't clear without debugging if we can always provide properties in this method (with caching) or it is intended in to always recalculate properties todo: for hotfix 23.2 I decided not risk to change behavior and only provide a fallback for shader files outside of Shaders module (i.e. for Player project files). Directly inside of ShaderLab block. Can be used for creation of HLSL blocks, Blend commands, Properties, Shader passes etc. Root of ShaderLab file. Can be used for creation of whole Shader commands. Expensive, avoid calling too many times.