elixir-type_check
real world example app
Our great sponsors
| elixir-type_check | real world example app | |
|---|---|---|
| 5 | 2 | |
| 510 | 870 | |
| - | - | |
| 5.9 | 0.0 | |
| 10 months ago | over 1 year ago | |
| Elixir | Elixir | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
elixir-type_check
-
Elixir and Phoenix can do it all
Use this until the one built into the language is ready. It has incredibly low performance impact too.
https://github.com/Qqwy/elixir-type_check
-
Do people actually use @spec? Do you find it useful?
I'm using type check so I'm using @spec!. But basically the same thing. It's great and it can catch nils when I don't expect there to be any. Great to ensure null safety even if the language itself doesn't support it. Just this alone is killer feature for me.
-
What is the Elixir language used for ?
Because Elixir has TypeScript types build in. It has strong types in runtime. 42 != "42", try doing this in TypeScript. Plus there's a library for runtime type checking. https://github.com/Qqwy/elixir-type_check
- TypeCheck: Fast and flexible runtime type-checking for your Elixir projects
real world example app
-
Phoenix namespacing conventions
After that, you're left with everything else in your application, much of which is interrelated on the data level. Using this repo as an example, you find that it has Accounts and then Blog as the primary namespaces (which make sense), which then leaves you with blog.ex which is a file containing a ton of database reading/writing/helper functions for all these different entities in the namespace (this is how the generators will also scaffold things, continuing to pile on the functions). It feel strange to me to have one giant file that forever grows proportional to the size of the namespace with so many concerns. Is it a good idea to split these things out (particularly when the ecto models aren't responsible for database queries in Pheonix) or am I just thinking about this the wrong way??
-
Phoenix
Getting Id token - here is some example: https://github.com/gothinkster/elixir-phoenix-realworld-example-app
What are some alternatives?
hammox - 🏝 automated contract testing via type checking for Elixir functions and mocks
phoenix-liveview-counter-tutorial - 🤯 beginners tutorial building a real time counter in Phoenix 1.7.7 + LiveView 0.19 ⚡️ Learn the fundamentals from first principals so you can make something amazing! 🚀
StreamData - Data generation and property-based testing for Elixir. 🔮
koans - Small exercises to discover elixir by testing
Drab - Remote controlled frontend framework for Phoenix.
harakiri - Help applications kill themselves
exp - Elixir library to statically inline expressions at compile time
oop - OOP in Elixir!
re - Elixir library for writing readable regexes in functional style
weather - A command line weather app built using elixir
mint - Functional HTTP client for Elixir with support for HTTP/1 and HTTP/2 🌱
elixir_koans - Elixir learning exercises