Hey @CounterStrike is there a way to see my team utility in the HUD? As an IGL it’s impossible to know the available spam without looking to my teammates (with cl_show_team_equipment) but as soon as I die the HUD shows that info on the top. Is this intentional?
@MichaelThiessen Im also an OG guy but I see the benefits.
Most complex logic is in the script so having this on top is useful (we dont have to scroll down on the file)
But more important, it’s a normal thing to define your variables/functions first to THEN render your template with those
@MichaelThiessen@vuejs Not really. For me its the same problem as teleports and globally available variables/components - it’s easy to lose control and to be confusing where information comes from.
IMO tou should either use props or stores to save information that tou will need in multiple places
@MichaelThiessen@vuejs Still migrating to Vue 3 in a fast paced environment where product always has priority, maybe the problem a lot of companies have nowadays. On the bright side, Vue 3 is heaven!
@MichaelThiessen@vuejs Still migrating to Vue 3 in a fast paced environment where product always has priority, maybe the problem a lot of companies have nowadays. On the bright side, Vue 3 is heaven
@ryanlpeterman IMO this should be a point of reference for managers. If tests, DX and good refactors go under the radar easily, a good EM will praise the work and make sure it doesn't get unnoticed.
@MichaelThiessen Yes. Hot topics should be discussed and opinions well-founded should be shared but as a teacher you should always share the available options
@MichaelThiessen@vuejs Awesome point
When we try to do everything in a single component we not only bump the complexity of that component to us and to others but we also make the components hard to test and to maintain.
Keeping components short and (if possible) dummy is my go to when building products