What version are you on? Aside from existing “pod” structure, the newer module unification feature follows a structure more in line with what you describe. Which addons are problematic? I don’t doubt they exist but…
I can see that argument... the same could be said about learning jsx as a layer on top of native js.. Before spa’s it was just interpolated strings rendered on the server.. people probably thought the same thing when…
what’s the point of resolving rest to graphql on the client if you’re not working with actual gql resources? what do you gain?
It was slightly off topic but I can understand it seeing as the example is in React/jsx and ember gets no love :) Personally jsx makes the hair on my body stand upright but that’s just me!
What version are you on? Aside from existing “pod” structure, the newer module unification feature follows a structure more in line with what you describe. Which addons are problematic? I don’t doubt they exist but…
I can see that argument... the same could be said about learning jsx as a layer on top of native js.. Before spa’s it was just interpolated strings rendered on the server.. people probably thought the same thing when…
what’s the point of resolving rest to graphql on the client if you’re not working with actual gql resources? what do you gain?
It was slightly off topic but I can understand it seeing as the example is in React/jsx and ember gets no love :) Personally jsx makes the hair on my body stand upright but that’s just me!