Open kaskranenburgQ opened 6 months ago
As discussed with @mabijkerk:
Ultimate goal is to have only a few general queries that will set certain groups / collection of nodes / etc., these queries can then subsequently be used in other queries that will be written in a more robust manner. This way, when making changes in projects these general queries should be checked properly (e.g. by using mechanical turk tests). When these queries are correct, then the chance of other queries to be incorrect will decrease significantly. Ultimate result: more robust, less error sensitive.
Options could be to make use of groups and filters:
We can start with trying out what works best for certain cost queries. In the future, improve robustness of other queries in a similar manner.
This issue has had no activity for 60 days and will be closed in 7 days. Removing the "Stale" label or posting a comment will prevent it from being closed automatically. You can also add the "Pinned" label to ensure it isn't marked as stale in the future.
At the moment, the cost sliders are structured in a hard coded manner. Here is an example of the query behind the slider "Investment costs coal plants":
It would be more future-proof to rewrite these slider queries in a structure using a filter so that new or changed nodes names are implemented automatically.