-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remove recommendation to use aget for JS object property access #15
Labels
Comments
https://clojurescript.org/news/2017-07-14-checked-array-access How is this issue going? |
I agree. I have known about this misinformation on the cheatsheet for some
time now. Hopefully will have some time for a fix tonight.
…On Sat, Jan 13, 2018 at 2:15 AM Jiacai Liu ***@***.***> wrote:
https://clojurescript.org/news/2017-07-14-checked-array-access
How is this issue going?
I think we need to remove this usage ASAP to avoid misguiding newbies.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAGAtQVTDSQmvN7H0tGpIombv-MCpZguks5tKFf-gaJpZM4OOlLo>
.
|
oakmac
added a commit
that referenced
this issue
Jan 13, 2018
oakmac
added a commit
that referenced
this issue
Jan 13, 2018
Great, I think we can also add goog.object/get, goog.object/set, goog.object/getValueByKeys, and put cljs-oops in External Library section |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
re: https://twitter.com/mfikes/status/882013594828800000
Should recommend using cljs-oops for JS object property access.
The text was updated successfully, but these errors were encountered: