You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was [planning](https://github.com/FlexMeasures/flexmeasures/discussions/763#discussioncomment-6500979) to document which attributes are actually relevant, and market_id would have to be added to the list.
Is it possible to replace the name market_id with consumption-price-sensor, for instance, so we get more consistency?
As @Flix6x said, this needs a db migration, a few code replacements and maybe a check within plugins we have, like the one we use for simulations.
Plus, maybe mentioning in the upgraded documentation that consumption-price-sensor can also live outside of the flex context as an attribute.
Or (my preferred option), we use flex-context["consumption-price-sensor"], for more consistency. I want us to look up flex-model and flex-context on either sensor or asset, and this way we can get rid of market_id with a comprehensive solution which will work for all other things, as well (capacity_in_mw would be part of flex-model, see #335 - we could tackle these together)
The text was updated successfully, but these errors were encountered:
Is it possible to replace the name
market_id
withconsumption-price-sensor
, for instance, so we get more consistency?Originally posted by @nhoening in #695 (comment)
As @Flix6x said, this needs a db migration, a few code replacements and maybe a check within plugins we have, like the one we use for simulations.
Plus, maybe mentioning in the upgraded documentation that
consumption-price-sensor
can also live outside of the flex context as an attribute.Or (my preferred option), we use
flex-context["consumption-price-sensor"]
, for more consistency. I want us to look upflex-model
andflex-context
on either sensor or asset, and this way we can get rid ofmarket_id
with a comprehensive solution which will work for all other things, as well (capacity_in_mw
would be part offlex-model
, see #335 - we could tackle these together)The text was updated successfully, but these errors were encountered: