Mads Nedergaard

The capacity change makes sense, the parser whoever is not quite as intended: it's supposed to query data about real-time production from an external source (have a look at other...

Let's get the capacity changes merged in and finish this PR, and then we can revisit the parser later :) Are you up for reverting the parser change and updating...

> I didn't have time to change anything today but I'll do it this weekend. > > However I think this will suffer the same fate as #4630 so I...

Thanks for doing this work! Unfortunately this change requires significant work on our backend, so we cannot support this update just yet. We'll close this PR for now, but return...

cc @pierresegonne, any idea why?

Copying the response from #4405 to here for visibility: > Note that it will probably still take a little while before we can update to python 3.10. We lock the...

I think this is awesome! The zone names cannot be changes (as we also use them for the API), but we can definitely find a solution that removes most of...

This PR breaks Chrome when trying to review it 😄 I'd like us to map out the different user journeys for working/changing these configurations to better understand the impact of...

Ugh, annoying that it jumps weirdly around :/ https://user-images.githubusercontent.com/3296643/170287521-ec91d85e-5a5f-494d-aaae-c67740f596a1.mp4 Dunno if it would make sense to switch to some package for this like https://github.com/naikus/svg-gauge? 🤔 (just first result when googling,...

Hmm, good point.. We've also been discussing switching the graphs to a more standardized React library (instead of the heavily customized d3 setup we current have), so maybe worth parking...