Not OP but a guide would be useful for contributing to existing libraries. For example, the websocket library is lacking some features (https://github.com/elm-lang/websocket/issues/14) that I would like to try and implement. The two things that suck right now: No documentation for the native framework, and, not sure if it would be in vain since Evan is highly opinionated (and rightly so) on API design, and I have no idea if whatever I implement would meet his standard.
On Monday, December 5, 2016 at 11:22:42 AM UTC-6, Richard Feldman wrote: > > No new thinking on that as far as I'm aware...what are you looking to > build? > > On Mon, Dec 5, 2016, 8:37 AM Wil C <[email protected] <javascript:>> wrote: > >> Do you know if there's going to be a guide on native modules? I just used >> elm-markdown as a guide, but I saw there were other conventions in other >> libraries with native modules. >> >> I understand the hesitation in giving a guide on an escape hatch to >> native, since people will instinctively reach for it. Just was wondering if >> there was new thinking on it. >> >> >> On Monday, December 5, 2016 at 8:19:14 AM UTC-8, Richard Feldman wrote: >>> >>> Looking at the evancz/elm-markdown >>> <https://github.com/evancz/elm-markdown> parser, that seems like a case >>> that warrants it, yeah. >>> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Elm Discuss" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/elm-discuss/nuR4NnCVcMs/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected] <javascript:>. >> 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
