[
https://issues.apache.org/jira/browse/SLIDER-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14264743#comment-14264743
]
Steve Loughran commented on SLIDER-648:
---------------------------------------
The reason for putting the options in under a tree of
components/COMPONENT1/mykey is
# it visibly isolates what's going on
# it lets us implement a basic overrride mechanism; I can set "mykey.value"=4
globally, and in COMPONENT1 override it to "5".
# if we add a cross-referencing mechanism, then we can explicitly look for
things like "update-interval" @{/components/COMPONENT1/mykey}" (the @{}) symbol
is what we are thinking of as $ already gets used in places. Again we need that
tree and basic inheritance to work.
Is there anything slider can't actually do with its current configuration model?
> Support component level properties
> ----------------------------------
>
> Key: SLIDER-648
> URL: https://issues.apache.org/jira/browse/SLIDER-648
> Project: Slider
> Issue Type: Improvement
> Reporter: Siyuan Hua
>
> Nowadays I could define properties like this
> global:{
> "site.COMPONENT1.mykey" : "myvalue"
> }
> That's better to define component properties in component section like this:
> components": {
> "COMPONENT1": {
> *"mykey": "myvalue"*
> },
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
