Inline uid to .gd/.shader/.shaderinc.

[Daylily-Zeleen]

The main idea can be referred to thsi thread,

• Get UID from ".uid" file first (for compatibility).
• Add a comment line to store UID in GDScript/Shader/ShaderInclude if ".uid" file is invalid.
• Scripts in “res://addons/” still using ".uid" files, avoid changing content of plugin's scripts.
• Add settings to enable this feature:
  • "filesystem/inline_text_resource_uids/gdscript"
  • "filesystem/inline_text_resource_uids/shader"
  • "filesystem/inline_text_resource_uids/shader_include"
• Add setting "filesystem/inline_text_resource_uids/compatibility/no_inline_text_resource_uids_in_addons" to disable this feature in "res://addons".

[AThousandShips]

How is this different from:

• Add optional GDScript UID comments #99090

[Daylily-Zeleen]

How is this different from:

• Add optional GDScript UID comments #99090

I forget that there have #99090 so I make this one.

Some differents:

• This pr has not any option to enable or disable this feature.
• This pr will keep exists ".uid" files.
• This pr still using ".uid" files in "res://addons/" to avoid change content of plugin's scripts. Can disable this feature in "res://addons/" for compatibility.

[AThousandShips]

I'd say this is fully a duplicate and the specific implementation should be discussed on the other PR

[KoBeWi]

This pr will keep exists ".uid" files.

It's the same in the other PR. You have to delete .uid files for the comments to be created.

This pr still using ".uid" files in "res://addons/" to avoid change content of plugin's scripts.

That's only useful if addons don't come with UIDs included. I think most active addons are already updated at this point.

[Daylily-Zeleen]

Let's discuss in the other pr.