On 4 Jun 2017, 13:39 +0200, José Valim <[email protected]>, wrote:
> I think this is a great idea. > > Question: if someone is using Ecto and Phoenix, and they need to open up a > bug in Ecto, how can they do so without all of the Phoenix metadata? > > That said, wouldn't it be better for each of those projects to introduce > report.ecto / report.phoenix individually? Then they have full control on the > report. If by any chance we see some duplication, then we can introduce > helper functions. That would be more flexible than wrapping the whole > functionality. > I was thinking about this and I'm not sure this is better. There might be some additional information, but if everything is properly sectioned, I don't think it's going to be a huge issue. It will also "just work" for projects that don't need to add additional information. Another thing to consider is that often, an issue created in phoenix is actually something wrong with ecto, so having all this information already there would be helpful. Having one task creates an excellent workflow - do you have any issues with something elixir-related? Run `mix report` and open an issue. That's it. With separate tasks, you need to figure out the appropriate task to run - first find out if it's even there. If we really want to push it, GitHub new issue link allows passing title & body query options to fill the template. I could imagine running `mix report phoenix` which would open an issue on the phoenix repo with filled template (provided project has the GitHub link). That might be going a bit too far, though. -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/4564c0ed-a1eb-4ccd-bc40-9fb018a9b4ab%40Spark. For more options, visit https://groups.google.com/d/optout.
