petal_components
lexical
| petal_components | lexical | |
|---|---|---|
| 6 | 4 | |
| 740 | 711 | |
| 1.8% | 7.3% | |
| 8.6 | 9.5 | |
| 20 days ago | 5 days ago | |
| Elixir | Elixir | |
| 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.
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?
lexical
-
Pinterest's simple tech stack to scale to 11M monthly users
[2] https://github.com/lexical-lsp/lexical
- Lexical Language Server 0.4.0 Released
-
Elixir and Phoenix can do it all
I’ve been writing Elixir for years and I can’t even think of the last time I had a language server crash…
Plus, these days there are many alternate LSP implementations besides Elixir LS:
https://github.com/lexical-lsp/lexical
https://github.com/elixir-tools/next-ls
-
Introducing Next LS and an elixir-tools update
How does this compare to lexical language server?
What are some alternatives?
Sobelow - Security-focused static analysis for the Phoenix Framework
next-ls - The language server for Elixir that just works. Ready for early adopters!
PhoenixBootstrapForm - Bootstrap 4 Forms for Phoenix/Elixir Applications
elixir-styler - An @elixir-lang code-style enforcer that will just FIFY instead of complaining
Tarams - Cast and validate external data and request parameters for Elixir and Phoenix
moon - Moon Design System for Elixir
Formulator - A form library for Phoenix
PinWork - PinWork(Pinterest for bloggers) built with ❤️ using Angular2 (4.0.0)
querie - Compose Ecto query from the client side
ExForm - Simplistic api wrapper for Typeform api without abusing macro/dsl
excessibility - Library to aid in testing your application for WCAG compliance automatically using Pa11y and Wallaby.
Formex - A better form library for Phoenix