Is such a module even necessary? Couldn't you just write a library that uses the existing http library? Then it could be published.
On Nov 29, 2016 11:36 AM, "Nick H" <[email protected]> wrote: > (I mentioned version 0.16 because I think that is when the native review > process was officially discontinued, but actually I bet the community > packages on the whitelist are older even than that.) > > On Tue, Nov 29, 2016 at 11:33 AM, Nick H <[email protected]> > wrote: > >> There is no process for adding new packages to the whitelist. Everything >> on there, besides some newer elm-lang packages, has been around since >> version 0.16. >> >> But that aside, you should never use native modules if there is another >> option. >> >> On Tue, Nov 29, 2016 at 10:58 AM, Ed Ilyin <[email protected]> >> wrote: >> >>> What if I'm going to write elm-firebase package - should I write it as >>> an effect module or native module to have a chance to be whitelisted? >>> >>> Ed Ilyin >>> >>> -- >>> 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. >>> >> >> > -- > 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. > -- 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.
