UX: extend permalink with costing options

[nilsnolde]

We have a couple of useful attributes we use in the internal router for permalinks, like profile. However, to be truly useful to power users is costing options support in the permalink. Currently we always reset any costing option when reloading the page. Code-wise this is probably pretty painful, also to maintain it in the future. It'd be great if there'd be some kind of integration test that'd catch when a new costing option/setting was added and fail if it's not considered in the permalink.

[lourduradjou]

Hi @nilsnolde , I’m interested in working on this.

Just to clarify the scope:

• Should all costing options be serialized into the permalink?
• Do you prefer flat query params (e.g., &fixed_speed=...)
  or a JSON-encoded parameter?
• Should we ensure backward compatibility with existing permalinks?

I’d also propose adding an integration test to ensure that
new costing options added in the future are included in the permalink logic.

Happy to start with a draft PR once direction is confirmed.

[nilsnolde]

I'd like to hear @mustaphaturhan 's opinion here. It's not very important honestly, it's very rare that I personally miss this feature. Mustafa can judge a bit better if the code changes would justify the result.

[lourduradjou]

Sure, please take your time. And @nilsnolde do we have any community discussion place like discord or slack? Could you share the link.

[nilsnolde]

Nope, for our own sanity Github is the only place for (targeted) discussions.