Skip to content
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

hx/f exceptions handlint #53

Closed
gavlooth opened this issue Jun 2, 2019 · 4 comments
Closed

hx/f exceptions handlint #53

gavlooth opened this issue Jun 2, 2019 · 4 comments

Comments

@gavlooth
Copy link

gavlooth commented Jun 2, 2019

when passing a nil value map {nil nil} (eg, when using select-keys with and the props have not been populated) with hx/f a doesn't support namespaces error occurs

@gavlooth
Copy link
Author

gavlooth commented Jun 2, 2019

Also i find the same problem on other instances, when i pash string props.

@lilactown
Copy link
Collaborator

Can you explain a bit more how you’re ending up passing {nil nil} to a component? I’m not sure I understand the select-keys example you mention.

FWIW, passing {:foo nil} should work just fine, but I currently believe passing anything other than a keyword as a key will error.

@gavlooth
Copy link
Author

gavlooth commented Jun 3, 2019

Seems that select-keys returns a {nil nil} map when no keys are found but i am not sure, i remember correctly.
However what you say make sence because i also have problems with string keys.

@lilactown
Copy link
Collaborator

In my REPL (latest CLJS):

cljs.user> (select-keys {} [:foo :bar])
{}

I can perhaps add some support for string keys. Is there a reason you're using them specifically?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants