Skip to content
This repository has been archived by the owner on Sep 8, 2020. It is now read-only.

Object given as ui-options shouldn't get assigned to #226

Open
jrencz opened this issue Aug 7, 2017 · 0 comments
Open

Object given as ui-options shouldn't get assigned to #226

jrencz opened this issue Aug 7, 2017 · 0 comments

Comments

@jrencz
Copy link

jrencz commented Aug 7, 2017

I decided to store an object that is common to some of my masked fields on a module.
Module gets imported to the controller module and the object is assigned onto the controller.
Then the object is passed to ui-options via template expression.

It happened that I defined the original module using Object.freeze. I got an error saying that It's not possible to extend the object. It seems like when expression in ui-options attribute gets evaluated defaults are assigned onto it. Correct behaviour would be to assign first defaults, then local overrides onto a fresh object each time.

@jrencz jrencz changed the title Object given as ui-options shouldn't get assigned Object given as ui-options shouldn't get assigned to Aug 7, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant