where you call om/transact! at all: om/transact! works through the
parser, and you'll have the storage-specific implementations there.
Does that make sense? I defer to anyone who's actually done this :)
Michael Glaesemann
grzm seespotcode net
--
Note that posts from new members are mo
t it's
> implementation from the UI.
Can you give a more concrete example of what you're trying to do? Say, the
built-in Om database vs DataScript or something like that?
Michael Glaesemann
grzm seespotcode net
--
Note that posts from new members are moderated - please be patie
to
hide implementation details (both on the web server and database sides) from
application logic.
I'm wondering if I've completely misunderstood your questions. In particular,
when I think persistence I think server side. Perhaps you're thinking of
storage on the client? Given that th
this patch on my todo list but won't be upset if
> someone beats me to it ;-D
The patch is already there :)
>
> Thanks Michael!
>
> Travis
>
> On Tue, Mar 4, 2014 at 9:17 AM, Michael Glaesemann
> wrote:
>>
>> On Feb 26, 2014, at 14:48, Michael G
On Feb 26, 2014, at 14:48, Michael Glaesemann wrote:
>
> On Feb 26, 2014, at 14:33, Travis Vachon wrote:
>
>> oh! I totally missed :hashbang "" - I'm pretty sure that'll do what I
>> want yep - thanks! I'll let you know if that doesn't do the
ent, then you don't target node, and you just use a preamble. That'd be
confusing, at least to me.
Perhaps just update the code to prepend #! unless :hashbang is "", or omit if
:hashbang is false?
>
> On Wed, Feb 26, 2014 at 2:23 PM, Michael Glaesemann
> wrote:
>>
ourcemap comment in the preamble?
That'd be an option, though it's also possible to set the value of the
hashbang. Does :hashbang "" do what you want?
>
> On Fri, Feb 21, 2014 at 2:14 PM, Michael Glaesemann
> wrote:
>>
>> On Feb 21, 2014, at 13:56, Davi
Fri, Feb 21, 2014 at 1:52 PM, Michael Glaesemann
> wrote:
>
>> Currently the :preamble and :target :nodejs compiler options are mutually
>> exclusive.
>>
>> I recently had a situation where I wanted to use a preamble with node: I
>> came across
>> a nodejs
at adds the preamble directly after the node hashbang.
If this looks like something that would be generally useful, I'm happy to
create a JIRA issue and attach the patch.
Cheers,
Michael Glaesemann
grzm seespotcode net
--
Note that posts from new members are moderated - please be pati
uot; to get it.
Thanks for the patient guidance :)
Michael Glaesemann
grzm seespotcode net
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you are subscribed to the Google Groups
"ClojureScript" group.
merick/clojurescript.test/pull/38
The updates to middleware are more procedural than I'd like, but I wasn't sure
how you'd want to handle it.
https://github.com/grzm/clojurescript.test/commit/2e46024e1e1d3501caa12a8c44c5bbd8806e0451
Let me know if you'd like any changes.
Che
On Jan 21, 2014, at 21:07, Michael Glaesemann wrote:
>
> On Jan 21, 2014, at 15:20, Chas Emerick wrote:
>
>> Correct, clojurescript.test only supports phantomjs and phantomjs-compatible
>> environments (e.g. slimer and derivatives) at the moment. As noted in the
>>
!
Nikita, Chas,
Thanks for the feedback. I understood that there's only a phantomjs runner, but
I guess I didn't fathom the full implications. I'll see what I can do with a
nodejs runner.
Cheers!
Michael Glaesemann
grzm seespotcode net
>
> Thanks,
>
> - Chas
>
cript I actually used in my code. Here I'm just requiring
cljs.nodejs: no code is actually being used.
I'd like to continue to use clojurescript.test, so any pointers
would be appreciated. I suspect I'm overlooking something simple.
I've included the relevant code below. If t
14 matches
Mail list logo
