om

Please ask the channel first, not @dnolen directly!
kardan 2017-06-19T11:53:55.367962Z

Any reason why I would not see a UUID printed in the console when using om/transact! ?

kardan 2017-06-19T11:54:58.381070Z

(as in the quick start Wiki entry)

2017-06-19T11:56:30.400787Z

@kardan I've seen it's hidden in later versions of Chrome. Try adjusting your log filters.

2017-06-19T11:57:02.407339Z

I no longer see it under 'Info', I have to change to 'Verbose'

kardan 2017-06-19T11:57:19.411131Z

You’re correct, thanks a million. Was starting to question my sanity

2017-06-19T11:57:22.411752Z

I'm not sure why because I believe the log level should be info.

oconn 2017-06-19T22:28:46.834855Z

Question about om-next / Datomic interaction. I'm sending my requests from the client over transit+json and I want to leverage Datomic's pull syntax. I have this working when I define all the parameters I want, but I am having difficulties using wildcard syntax. Anyone have a suggestion or link to an example if this is possible?

oconn 2017-06-19T22:29:59.850221Z

example of what I want to be able to define on the client: (:user/by-id '[* {:user/permissions [*]}])

2017-06-19T22:39:34.970105Z

I don't believe wildcards are allowed since they're written as a symbol and afaik only keywords and maps are allowed in a query. Also, the point of queries are for the components to specify what they expect and wildcards would break that. Just declare all the keywords you need.

oconn 2017-06-19T22:43:06.013547Z

That makes sense, thanks.