Query Params as derived data

[NullVoxPopuli]

rendered

This RFC is part of a series of RFCs to lead to the deprecation of controllers entirely. For more about how I imagine that happening, let's talk on Discord / keep the RFCs themselves focused on the topic they're about.

Related RFCs:

• Arbitrary Query Params

  • would affect the proposed Ember Guides changes mentioned in this (Query Params as derived data #712) RFC, in that, all mentions of controllers would be removed (after both Query Params as derived data #712 and Arbitrary Query Params #715, an app can opt out of controllers entirely)
  • Query Params as derived data #712 and Arbitrary Query Params #715 are closely related

• An Alternative to Controllers

  • explores some ideas that are similar to what have been discussed recently with template-imports in the #st-template-imports channel in discord
  • needs a good amount of revisions

[jkusa]

I like this direction. Do you consider how query params are declared in scope for this RFC?

[NullVoxPopuli]

Maybe discussing them is -- as it's def part of the learning story! :)

I also don't think query params should have default values (especially since that state is entangled with the controller).
For the URL to be the source of truth, to access a QP from within a component would require something like this:

get category() {
  return this.router.currentRoute.queryParams.category ?? 'default value';
}

[NullVoxPopuli]

related: #715

[sly7-7]

I've quickly read (maybe too quick), but I can't see what happen to the { scope: 'controller' } thing.

[NullVoxPopuli]

I've quickly read (maybe too quick), but I can't see what happen to the { scope: 'controller' } thing.

the setting doesn't affect the derived data patterns -- here is an example: https://ember-twiddle.com/567b7acf47448cee1f63fcb36e82cd66?openFiles=controllers.articles%5C.js%2C

[wagenet]

@NullVoxPopuli is this just waiting on core review?

[NullVoxPopuli]

yup

[wagenet]

Thanks for spending the time writing this RFC! Given the significant number of concerns around routing, we’re going to be completely revamping the router as part of Polaris. This RFC won’t directly apply to the new router so we’re going to move this PR to FCP to Close. But don’t worry, your work here was not in vain! We will be keeping track of this RFC and others like it to make sure that the concerns it aims to address will be covered in the new router. Your work here does a significant service to us in this regard!

[NullVoxPopuli]

Fwiw, this RFC still serves as a source of (imo) better documentation for managing query params than we have today in the guides.

(this was a documentation only RFC)

[NullVoxPopuli]

Latest example I have: https://github.com/NullVoxPopuli/game-of-life/blob/main/app/services/display.ts

[sukima]

This is mixing the URL APIs and string concatenation.

I'd love to see Ember support the Web standard URL APIs for this.

Something like this would gain the benifits of proper URI encoding.

let url = new URL(this.args.href, 'thismessage:/');
url.search = stickyQPsToQueryString(…);
return url.href;

[NullVoxPopuli]

yeah, the example is out of date -- using URL is very good, and I wrote all this before I started using URL, URLSearchParams, etc.

This is all userland code tho, so folks should feel free to use URL 🎉

[sandstrom]

Given the significant number of concerns around routing, we’re going to be completely revamping the router as part of Polaris.

Where can I find information about this Polaris plan for routing?