If you’re initially looking for something small to contribute on there is an issue that I logged with ja_resource that I haven’t had time to fix yet. I would be happy to help out and point you in the right direction. If you were hoping for something different or bigger maybe take a look at code triage and you should be able to find something of interest on one of those repos.
It should be simple enough: find some CSV library, get data from database, put into CSV format, write as response. Should also check if data can be too big to fit in memory comfortably and change approach accordingly.
I’m not sure if you are new to Programming or just Elixir? If just Elixir I have recently categorised a load of issues on a project I have that is to showcase deploying elixir with docker. Elixir and deployment is an open question at the moment, so I hope for this to become a useful resource.
If you are new to programming in general, help would of course be welcome, but I would suggest leaving the world of deployment issues for the moment.
Hi, this seems interesting, I think I’ll consider it for a contribution, thank you
I am new in Elixir , but not in programming. I am looking for programming contribution (e.g. fix bugs or add new features). elixir-on-docker is a sort of integration between existing projects in order to provide a stack where we can build application cloud native on top of it. Right?
What I am looking for are projects like ja_resource or code-stats. For example, a Phoenix based project could be interesting too, because I’d like to learn something about Phoenix. Libraries are also welcome
More or less right. It’s build on an alternative stack to plug/phoenix etc, you might want to start more in the mainstream.
Some of the issues are Elixir programming 100%, I just didn’t want to confuse a newbie with too many technologies in one go and an appreciation of Docker would be probably necessary.
As you can see here I tried to propose a fix to the issue you talked about.
Let me know what do you think.
The strange thing I noticed is how the maintainer of ja_resource decided to test the library. He or she introduced a fake implementation of Ecto.Schema and Ecto.Repo, this makes the test to be potentially “false positive”, cause when we will try to use a newer version of Ecto, the tests will continue to use the fake implementation and obviously continue to pass, with no feedback about possible regressions.
Another problem I found is, since we have to use the fake implementation for our tests we are forced to maintain and update the code twice (our application code, and the fake implementation) .
In general, it is not recommended to fake what you cannot control. In this case I would propose a new issue there to invite to remove the fake implementation and to use the real Ecto. Just because this library is strictly coupled with Phoenix/Ecto.
I haven’t looked into the tests before but I agree it’s a bit strange to fake Ecto. I’m guessing the author has done this so they don’t need a database for testing, though I would argue the library shouldn’t depend on Ecto in the first place which would allow it to work more generically. I think there is definitely scope for improvement here and if you have the time and willingness to work on it, I’m sure the author would be open to suggestions.
It was a fantastic journey in learning something more about Elixir and Phoenix, so I was able to contribute to Code-Stats too, here you can find the merge request I proposed: expose an API for pulses data export. It was very helpful to have @Nicd with me during the live streaming session
I am looking forward to continue with my contribution on Code-Stats and ja_resource.
But I am looking for other projects too, let me know by replying this thread, or open an Issue to this project joebew42/twitch by proposing an Elixir project. If you have an Elixir project or do you want help with an Issue, please let me know! I will be glad to help you folks