You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Converting a primitive value to a string is a very common need. Godot supports this with the str() function, but this is not documented anywhere I expect most users would think to look for it. It's not mentioned on the page for the String type, nor on the pages for any of the types you might want to convert from. Rather it's only mentioned on the GlobalScope page.
I would suggest that if a function is specifically relevant to certain types or classes, it should be mentioned on the page about that type/class, even if it's not actually a part of it.
The text was updated successfully, but these errors were encountered:
What do you mean hidden? It's documented right here? These methods aren't secret in any way. I don't think it makes sense to mention every function that is related to each type, the str function has nothing really to do with any specific type, no more than var_to_str has
I don't think it's unreasonable to want str(), str_to_var(), and var_to_str() documented with the rest of the functions related to strings, on the String class ref page. But since the class reference is generated from the functions that are actually in a class, we can't randomly move functions or document them in two different places.
In this case, we could maybe add a short sentence on the String class introduction that links to these three functions?
Converting a primitive value to a string is a very common need. Godot supports this with the
str()
function, but this is not documented anywhere I expect most users would think to look for it. It's not mentioned on the page for the String type, nor on the pages for any of the types you might want to convert from. Rather it's only mentioned on the GlobalScope page.I would suggest that if a function is specifically relevant to certain types or classes, it should be mentioned on the page about that type/class, even if it's not actually a part of it.
The text was updated successfully, but these errors were encountered: