My initial tests with the code shows that it crashes pretty heavily. I was trying to use HTML5 urls rather than #/, so I made these changes in the example code. I should have dropped 9, not 8, but the result was a complete hang. ``` toUrl : Int -> String toUrl count = "/counter/" ++ toString count -- "#/" ++ toString count
fromUrl : String -> Result String Int fromUrl url = String.toInt (String.dropLeft 8 url) ``` On Thursday, 26 May 2016 20:28:54 UTC+2, Gage Peterson wrote: > > I was too, a bit confused to find out that it didn't show up in the > subscriptions... and the fact that we're aren't using Html.App anymore. Not > a huge deal but I think it would be nice to like only 3 or 2 ways to set a > project to lower the cognitive load. Not a huge deal considering how > closely related everything is in Elm. > > The "s" command failed to be looked up properly by elm-oracle (probably a > bug either in the vim config or oracle), I think "strict" or perhaps > "exactly" would be a better name. People can always alias it if it gets too > long. I'm a big fan of aliasing in the local scope of function rather than > at the Library level. > > Very strong work however! It was very easy to understand overall. 100x > better than what I've seen in JS in complexity and size. Bravo! > > On Thursday, May 26, 2016 at 4:09:35 AM UTC-6, Fedor Nezhivoi wrote: >> >> Shouldn't "s" function be named as "strict"? >> >> 2016-05-26 12:10 GMT+06:00 Bogdan Popa <popa.b...@gmail.com>: >> >>> I've updated elm-route's example app to use `elm-lang/navigation`[1]. >>> The diff[2] looks pretty good if you ask me. Thanks guys! >>> >>> 1: https://github.com/Bogdanp/elm-route/tree/master/examples/app >>> 2: >>> https://github.com/Bogdanp/elm-route/commit/2b33522c09213b1197fe9512c9ac3fc745b1f16d >>> >>> Evan Czaplicki <eva...@gmail.com> writes: >>> >>> > On Friday, Noah and I worked on "updating elm-history" so that folks >>> can do >>> > "routing" with Elm 0.17. The results are these libraries: >>> > >>> > - elm-lang/navigation >>> > <http://package.elm-lang.org/packages/elm-lang/navigation/latest/> >>> > - evancz/url-parser >>> > <http://package.elm-lang.org/packages/evancz/url-parser/latest/> >>> > >>> > I think they will cover the core functionality in a way that also >>> promotes >>> > healthy architecture. If you disagree, I ask that you *use* these >>> libraries >>> > before you share your opinion (or ideally the particular scenario you >>> are >>> > having trouble with). >>> > >>> > >>> > Details >>> > >>> > The elm-lang/navigation library is the core thing. It lets you get >>> notified >>> > about changes to the address bar. This may be the user typing in there >>> or >>> > pressing the forward and back buttons on the browser. It also lets you >>> > "navigate to new URLs" so you can go to new URLs without reloading any >>> > assets. >>> > >>> > The elm-lang/navigation library is designed such that you can parse >>> URLs >>> > however you want. You can see a basic example of that here >>> > <https://github.com/elm-lang/navigation/tree/master/examples>. The >>> > evancz/url-parser library is meant to handle more complex cases. You >>> can >>> > see a bit of that in this example >>> > <https://github.com/evancz/url-parser/tree/master/examples>. >>> > >>> > My URL parser is intended to be a baseline for exploration. There are >>> > probably cases it does not cover well. My goal right now is to point us >>> > towards good API design, not to be *the* URL parser. >>> > >>> > >>> > Thanks >>> > >>> > Big thanks to Noah for working through all this with me! And thank you >>> to >>> > Aaron who helped review and talk through the API we ended up with. >>> These >>> > were fun to work on :D >>> > >>> > -- >>> > You received this message because you are subscribed to the Google >>> Groups "Elm Discuss" group. >>> > To unsubscribe from this group and stop receiving emails from it, send >>> an email to elm-discuss...@googlegroups.com. >>> > For more options, visit https://groups.google.com/d/optout. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Elm Discuss" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to elm-discuss...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Best regards, >> Fedor Nezhivoi. >> > -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
