Arthur Goldsmith
Arthur Goldsmith
For those looking for a work around you can force your ace-build in your package.json by typing: ```json "resolutions": { "ember-ace/**/ace-builds": "1.4.1" ```
Yeah this is some _wonky_ behaviour. Completely unexpected. *If the precision is zero*, the unmasked output should an *integer*, always.
a11y should be a top priority. Happy to help with some general guidance.
Same issue after having upgraded to Ember 3.28/4 - I now have relative paths for the sourcemaps where it used to be absolute paths.
@runspired does @VincentMolinie fix go far enough to address this issue, i.e. will ModelFragments work on 3.28.x/4.x going forward?
@jrjohnson that's always been the problem with ember components, a ton of rendering overhead. A lot of small components (like a ton of icons!) is like death from a 1000x...
@jrjohnson we couldn't find any proper tools, so we decided to come up with a setup that illustrates the basic overhead of initial renders using the 3 types of components...
I believe so. I'm no glimmer rendering expert, but this stuff adds up quickly. We have a page with about 120 cards, and in each of the cards there's a...
@jelhan the overhead almost has to be the same; _something_ has to represent the component one way or the other. As far as I know, the net gains by moving...
Ah, love this solution! Easy way to opt into sprites.