[Feature Request] enable explicit exclusion of properties from the UIModel functionality about aurelia-ui-framework HOT 4 CLOSED

@avrahamcool for that purpose I'm excluding all properties prefixed with a double underscore (__).
I haven't yet had the chance to spend time on the data-model and data-source implementations. maybe we should look into the possibility of adding a decorator '@Private' to declare the property definition as 'enumerable: false'

Object.defineProperty(this, {
   'propName': {
   writable: true,
   enumerable: false
   })

from aurelia-ui-framework.

indeed I saw that in the code.

but what about the properties that you want to bind into, and you don't want them to be active in the dirty checking/serialization etc..
it's ugly to have them with __ in the html/js.
a cleaner way would be to pass a parameter that tells the model to explicitly exclude them.

a Private decorator would suggest that a property is not accessible from outside of that class, in that case that not what we mean.
but the decorator approach is nice and elegant, maybe a different decorator name?

from aurelia-ui-framework.

I agree the current approach is a bit ugly but when I added it I was just looking for a quick-fix solution.

as for the name for a decorator, yes it must not say private instead something to signify non-serializable

from aurelia-ui-framework.

Added @serializable() decorator for UIModel properties.

Fixed in Version 4

from aurelia-ui-framework.