[DOC Release] Mark ObjectProxy as public

[joeruello]

Maybe a controversial one, defiantly a "power user" feature. Seems to be used a lot in the real world, but I don't know if moving forward it will continue to be supported.

Also not sure of the relationship to ES6 Proxies, maybe a possible replacement moving forward?

[stefanpenner]

My vote is to keep this private for now. Would love to here other thoughts

[btecu]

We use this heavily along with ArrayProxy. They are extremely useful for dynamic tables and are helpful for components because they allow them have their own state without mutating the model.

[stefanpenner]

We use this heavily along with ArrayProxy. Their extremely useful for dynamic tables and are helpful for components because they allow them have their own state without mutating the model.

An alternative, and significantly more flexible approach: https://github.com/stefanpenner/ember-state-services

[btecu]

That may work for some state but it would be a lot more verbose to use compared with ObjectProxy. Also, it doesn't replace ObjectProxy and ArrayProxy functionality.

[stefanpenner]

@btecu verbose merely indicates more work is needed to polish that use case.

[joeruello]

That's a pretty cool addon, but I can imagine using ObjectProxies as states. Seems more of a better way of managing state objects rather than a replacement.

Also currently lacks a way to iterate over states, but I'm sure that's trivial to implement.

[stefanpenner]

Ya. Infact the default example uses a proxy :p

[dukex]

Why ObjectProxy is private? I never noticed it, and I used this class today after see the ember-simple-auth(session.js) uses too

[joeruello]

@dukex: #11362 enforced marking docs explicitly to end confusion on what is Public/Private API. I'm having a look through and flagging code I think may have been incorrectly marked.

[rwjblue]

I think this should be marked public (since it is essentially defacto public at this point anyways), and we should go through a deprecation phase if/when we decide to remove it in the future.

[sandstrom]

Great, thanks! We've used it for some advanced things, it's very handy!

[toranb]

public +1

[greyhwndz]

public +1

[pixelhandler]

More background… emberjs/rfcs#80