[GitHub] ahgittin commented on issue #119: [WIP] tables should run with their own scope

[GitBox <gi...@apache.org>]

ahgittin commented on issue #119: [WIP] tables should run with their own scope
URL: https://github.com/apache/brooklyn-ui/pull/119#issuecomment-468741118
 
 
   the effect of `scope: true` is to create a new scope that prototypically inherits from the parent scope.  i think this is what we want in order to have the table's `scope.ctrl` be unique from another instance of table in the parent.
   
   it can still see all fields from the parent _that were defined when the table was created_.  in worst case, a caller/parent may have to initialize a field in the scope prior to creating the table (eg in the parent's controller) whereas previously they did not (since the scope was shared) and scope fields could be lazilly initialized.
   
   i've tested with complex tables and with a one line fix to initialize a scope field to be a null list, it works fine with `{scope: true}`.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services