dag 13 januari 2017 09:13:25 UTC+1 schreef Marco Perone:
>>
>> Coming back to my original question, supposing we have two mutually
>> recursive types, they must be in the same module and hence in the same
>> file, right?
>>
>
> Yes, that is what I would think too.
At the moment the debugger is a great instrument to keep track of all the
Messages in an application and to reproduce them.
Still sometimes, when there are a lot of Messages, it's not easy to search
through all the present information. I think that a good way to improve on
this would be to h
Coming back to my original question, supposing we have two mutually
recursive types, they must be in the same module and hence in the same
file, right?
I would argue that it would be nice to have the possibility to define
mutually recursive type in different files at least, if not in different
l this type recursive, it looks like an infinite type.
>
> On Fri, Dec 30, 2016, 03:29 Marco Perone wrote:
>
>> I have two types
>>
>> type alias Player =
>> { ...
>> , team : Team
>> }
>>
>> ty
I have two types
type alias Player =
{ ...
, team : Team
}
type alias Team =
{ ...
, players : List Players
}
which clearly have a circular dependency. I am duplicating data and I am
doing that on purpose.
Now the question is: is it possi
you could just add a `value` to your input field like
input [ onInput NewContent, value inputStr ]
and then reset the `inputStr` value when you confirm the submission
Confirm ->
{ model
| state = WaitingForSubmit
, inputStr = ""
Some days ago I had an idea, which I don't know if it's worth exploring, so
I'll just share it here and ask for some feedback.
Thinking about how to handle only valid state of an application, I tought
it would be nice if, for every function, we could be able to specify
precisely its domain, ins
not have the
> possibility to fail when simply responding to facts. Not sure if plus/minus
> overflow in Elm (in JS, they flip sign on overflow), but other kinds of
> operators could.
>
> On Wednesday, August 17, 2016 at 11:32:27 AM UTC-5, Marco Perone wrote:
>>
>> Hi!
about how huge the model.write
> could get considering it saves every event ever. Say in a given chat app
> this could get amazingly huge. How would that be handled in this pattern?
>
>
> On Wednesday, August 17, 2016 at 10:32:27 AM UTC-6, Marco Perone wrote:
>>
>> Hi!
>
Hi!
I was eventually able to read carefully the thread and give some thoughts
about it.
@kasey, I had a look to your Gist and it looks really interesting! Some
notes about it:
- I think it would be better to store in the parameter of the Fact's the
increment, and not the state of the applicat
Thanks Ian, elm-markdown did the trick!
2016-07-28 0:46 GMT+02:00 Ian Mackenzie :
> In this particular case, if you're just using highlight.js to highlight a
> block of code, you might also be able to use evancz/elm-markdown (
> http://package.elm-lang.org/packages/evancz/elm-markdown/3.0.0/). Yo
Hello everybody,
I am building an application in Elm and I need to call an external JS
library that interacts directly with the DOM (in my case, highlights a
section). I built a port to communicate from Elm to Javascript
and, on the Javascript side, I'd like to call my external library as soon
12 matches
Mail list logo