We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
#js {}
#js []
Construct JS objects new . (new js/Date args*) (module.MyType. args*)`
new .
Possibly also explicitly document js/ to explain/remind that it is used to access variables in the global scope?
js/
Also ^:export should be perhaps mentioned?
^:export
Perhaps also mention goog.object/set, get (that are advanced-compilation save variants of .-, now that aset can truly only be used for arrays)
goog.object/set, get
.-
aset
The text was updated successfully, but these errors were encountered:
Good ideas 👍 I have been thinking for a while now that the interop section could be improved.
Ideally, #js {} and #js [] should also have a tooltip (which should also highlight the differences from js-obj)
What are the differences between #js {} and js-obj ?
js-obj
Sorry, something went wrong.
#js {:prop 123} => {"prop": 123}
oakmac
No branches or pull requests
#js {}
and#js []
should also have a tooltip (which should also highlight the differences from js-obj)Possibly also explicitly document
js/
to explain/remind that it is used to access variables in the global scope?Also
^:export
should be perhaps mentioned?Perhaps also mention
goog.object/set, get
(that are advanced-compilation save variants of.-
, now thataset
can truly only be used for arrays)The text was updated successfully, but these errors were encountered: