sandstrom

> Export a new value, trackedClassic, from @ember/object/compat. This would only be usable as a classic decorator in classic classes, and the current form of tracked() would still be deprecated....

I'm not a big fan of prettier for JS code (we use ESlint). Haven't tried out prettier for handlebars, so can't judge it. One question though, will it be possible...

How about keeping it as an optional addon, just like it is today? I.e. anyone who needs it can add it to their app. Just like e.g. i18n addons (the...

I think it would make more sense to have a clear accessibility section on the website, where addons etc. are mentioned. So that those who need to build an accessible...

How about sticky query params? Wouldn't exist in this mode, I assume, but what would a user-space implementation look like? Same question for "default query params". When doing refresh on...

Some followup questions: With sticky, how would that work with links? A `{{link-to` wouldn't know that the remembered/sticky query param for route `/users` is `?sort=last-name`. Basically, you couldn't render `Users`...

@gnclmorais the threat model for a single page app is somewhat different from Rails, so I don't know if something like strong params would necessarily make sense here. Common vectors...

@gnclmorais I agree regarding documentation, self-documenting code would definitely be useful + agree that whitelisting params is a good idea (but not primarily for security).

Good idea!

This is probably an unpopular point of view, but I think there are other areas that should be prioritized over accessibility. Here are three examples: 1. Any of the many...