It's not a good idea to take value from configuration:
[16:55:34] <Evgeny Mandrikov>
BTW, Simon configuration returns value from global configuration or from project?
[16:57:05] <Simon Brandhof>
[16:57:15] <Evgeny Mandrikov>
looks like from global
[16:57:35] <Simon Brandhof>
looks like too
I'm looking for the way to load real project conf
[16:58:41] <Evgeny Mandrikov>
So, for now text "Last xx days" shows trash
[16:59:33] <Simon Brandhof>
well, api is not good enough. You have to use Propery.value('xxxx', <project_id>, <default value>)
[17:00:06] <Evgeny Mandrikov>
And what if property inherited from general?
[17:00:09] <Simon Brandhof>
but there is another pb
that's it, and for modules/packages too
[17:00:54] <Evgeny Mandrikov>
So I think that for now it would be better just remove this text. WDYT?
[17:01:14] <Simon Brandhof>
usually we save all data to display as measures
because if you change your config, displayed data are not consistent with conf
[17:05:02] <Evgeny Mandrikov>
Do you think that saving such value as measure is a good idea?
[17:05:52] <Simon Brandhof>
not really but we can imagine saving a measure with all the properties used during the analysis
that's not the first time we need such data
this measure would be automatically saved by the core and helpers would be added to gwt and rails api
[17:08:24] <Evgeny Mandrikov>
I don't want to save complex data for now - it will require helper parser
I think it would be better to simply remove this text for now and create issue for next major version.
[17:09:35] <Simon Brandhof>
list of key=value separated by commas, or some simple json. Of course that's not the responsability of your plugin. So now the best way is to not use the property