elixir-type_check
petal_components
Our great sponsors
| elixir-type_check | petal_components | |
|---|---|---|
| 5 | 6 | |
| 510 | 740 | |
| - | 3.2% | |
| 5.9 | 8.6 | |
| 10 months ago | 14 days 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
petal_components
-
Elixir and Phoenix can do it all
There are component libaries for LiveView.
https://github.com/petalframework/petal_components
https://github.com/coingaming/moon
I personally wouldn't use React for components in LiveView, you are just adding more complexity to your application for no reason. It really not that hard to build components using JS and LiveView. In the end you get less complex components than what you would get with react.
-
Anyone interested in writing a Component Library for Phoenix
You might also look at the PETAL components and ponder improving their accessibility (or the default components that come with the latest version of Phoenix, or any of a number of other UI toolkits).
-
Making a CheckboxGroup Input
Nothing stops you from creating 1 component per file. That's what Petal Components library is doing for example: https://github.com/petalframework/petal_components/tree/main/lib/petal_components
-
Something similar to Vuetify for Phoenix LiveView?
Have you looked at https://github.com/petalframework/petal_components?
-
Petal - A HEEX component library using Tailwind
Homepage: https://petal.build/docs Github: https://github.com/petalframework/petal_components The goal is to have a library of components out of the box ready to go so you can start focusing on solving your clients (or startups) problems instead of getting bogged down in design/css. Write components like this:
- Anyone writing a live view component library? How do you solve testing?
What are some alternatives?
hammox - 🏝 automated contract testing via type checking for Elixir functions and mocks
Sobelow - Security-focused static analysis for the Phoenix Framework
real world example app - Exemplary real world application built with Elixir + Phoenix
PhoenixBootstrapForm - Bootstrap 4 Forms for Phoenix/Elixir Applications
StreamData - Data generation and property-based testing for Elixir. 🔮
Tarams - Cast and validate external data and request parameters for Elixir and Phoenix
Drab - Remote controlled frontend framework for Phoenix.
Formulator - A form library for Phoenix
exp - Elixir library to statically inline expressions at compile time
PinWork - PinWork(Pinterest for bloggers) built with ❤️ using Angular2 (4.0.0)
re - Elixir library for writing readable regexes in functional style
querie - Compose Ecto query from the client side