Treat POJOs as Object.seal()'d JS objects

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: P3
    • 9
    • Affects Version/s: 9
    • Component/s: core-libs
    • None

      We need to treat POJOs as if they were JS objects that had Object.seal() invoked on them. Specifically, they're not extensible and their properties are not configurable. In terms of observable behavior, we should be throwing a TypeError when attempting to set a non-existent property on a POJO when in strict mode.

        1.
        		 With strict mode, bean property assignment of a non-existent property should result in TypeError Sub-task Resolved Sundararajan Athijegannathan  

            Assignee:
            Attila Szegedi
            Reporter:
            Attila Szegedi
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: