Integer to string casting and more string blocks

[DoomTas3r]

Code_It_All made this video using version 0.8.0, but could not cast an integer to a string.

Perhaps make all string parameters accept only strings or improve implicit casting
Parser Error: Value of type "int" cannot be assigned to a variable of type "String".

A Text category could be added for these string-related blocks:

1. (float) to string
2. length of (string)
3. letter (integer) of (string)

And maybe more complex blocks:

5. replace (string1) with (string2) in (string3)
6. slice (integer) of (string1) split by (string2)

And finally, the concat block's label could change to differentiate from the add block, for example: join (string1) (string2)

The current concat block allows both strings and integers to be added, but it compiles to string + integer, which produces an error
Parser Error: Invalid operands "String" and "int" for "+" operator.

[manuq]

Code_It_All made this video using version 0.8.0, but could not cast an integer to a string.

First off, let's fix the bug. PR #352 addresses the issue seen in the video.

On top of that, more text blocks would be welcome. Here is my attempt at "to string" which works with integers and floats. Ideally we would allow any type in its slot. I guess we could make the parameter type optional in display_template to allow any type: {value} to string instead of {value: INT} to string.

[gd_resource type="Resource" load_steps=2 format=3 uid="uid://d2eq3sdk61wkk"]

[ext_resource type="Script" path="res://addons/block_code/code_generation/block_definition.gd" id="1_g3t5i"]

[resource]
script = ExtResource("1_g3t5i")
name = &"to_string"
target_node_class = ""
description = "Format the value to String.

Advanced: A format string can be specified."
category = "Log"
type = 3
variant_type = 4
display_template = "{value: INT} to string | with format {format: STRING}"
code_template = "{format} % {value}
"
defaults = {
"format": "\"%s\""
}
signal_name = ""
scope = ""
is_advanced = true

[DoomTas3r]

@manuq Based on your attempt, here's my version, which is closer to what I envisioned:

I like the idea of conveniently accepting any type, and in contrast, my version can limit what type can be accepted. I don't know if there would be a reason for that, which is why I'm leaning towards your version.

Here's the branch with my version if you want to look at it:

https://github.com/DoomTas3r/changes-block-coding/tree/to-string-block

[upost]

It would be really nice to not only have this in log text, but also as an int-to-string node or even a format string node, so we can show int values (like tha player's score) in a label.