Break it up! Improving Your Godot Code Using Components
Break it up! Improving Your Godot Code Using Components
Here's a tutorial I wrote on using components to help keep your code organized.
Why are people still using string references? Like in the case of "Bumpable" - this could be a class name and reference could be via the class name instead of checking the node name by string. String references are super dangerous, as you will get a potential error only at runtime if you make a typo, IDE can't help you. Don't get me wrong - I like the idea behind component pattern and I use it myself sometimes, but the execution could be better in my opinion, unless I'm missing some obvious reasons for doing it this way.
That would definitely be an improvement, using classes is probably more robust. In my case, the project wasn't too huge and it was solo, so I never hit issues with string references.
@mrsgreenpotato @TheLongPrice Isn't the string reference just in the GetNodeOrNull call? I prefer to just export the nodes I need, so I don't build up Node-structure dependencies in the code. Therefore I don't have "Magic strings" in my code (almost) at all.
Correct, I'd also use exported values if possible. But that isn't flexible enough in some cases, because you'd need to individually export all possible attributes that the node might have.
For it to be more flexible, you could have something like this:
for child in get_children(): if child is ClassNameHere: return childThat would give you the same result as described in the article, without string reference. You could make a static func for it and call it a day :)
Thanks duder
Nice! I like it!
Thank you! I just started on a new project and it felt nice to remind myself what worked well in the previous one.