Usage Information

Nuke 10, SDK 10, TFM 10, Linux (Any OS)

Description

Consider a solution structure like this, where solution folders are numbered:

The source generator that creates a type-safe structure, seems to double-escape, and trips:

This can quickly be repro'd, by changing Nuke's own slnx file, by adding a numeric prefix to the "misc" folder name:

With the same result:

I'm happy to help with a PR, but I'd like a little guidance in the proper direction.

Reproduction Steps

Have a solution (slnx) file with a folder that starts with a number (like "00-misc").

Expected Behavior

Property types in the generated solution structure should be correct.

Actual Behavior

Solution folder property types seem to be escaped twice, and result in a type that does not exist ("__1_Sln" instead of "_00_Sln").

Regression?

Kind of, as on previous versions, this did work properly, but it also relates to the move from ".sln" to ".slnx".

Known Workarounds

Not using numeric prefixes in folder names. "S00-Sln" works, where "00-Sln" does not.

Could you help with a pull-request?

Yes