is AshPyro maintained?
I was trying to use pyro_components which in turn uses pyro . Pyro.Overrides modules is not present , hence pyro_components does not compile.
This is believed to be implemented via Spark. I don't know the author's handle here.
I wanted to take ash_pyro_components for a spin to see what kind of data tables / forms it would create. But stuck in compilation phase.
GitHub
GitHub - frankdugan3/pyro_components: Extensible Phoenix components...
Extensible Phoenix components, built with Pyro. Contribute to frankdugan3/pyro_components development by creating an account on GitHub.
GitHub
GitHub - frankdugan3/pyro: Compose extensible components for Phoenix.
Compose extensible components for Phoenix. Contribute to frankdugan3/pyro development by creating an account on GitHub.
6 Replies
@frankdugan3
I updated dependencies in a few of them
https://github.com/TwistingTwists/pyro_components
https://github.com/TwistingTwists/ash_pyro_components
https://github.com/TwistingTwists/pyro
GitHub
GitHub - TwistingTwists/pyro_components: Extensible Phoenix compone...
Extensible Phoenix components, built with Pyro. Contribute to TwistingTwists/pyro_components development by creating an account on GitHub.
GitHub
GitHub - TwistingTwists/ash_pyro_components: Automatic rendering of...
Automatic rendering of AshPryo DSL. Contribute to TwistingTwists/ash_pyro_components development by creating an account on GitHub.
GitHub
GitHub - TwistingTwists/pyro: Compose extensible components for Pho...
Compose extensible components for Phoenix. Contribute to TwistingTwists/pyro development by creating an account on GitHub.
I am currently rewriting the entire suite of libs, and it will be a while before it is ready to work (hobby project). The current releases are tied to old versions of Phoenix and Ash, so I'd recommend against using it ATM. You can follow my progress in #pyro
I see. would it be possible to push Pyro.Overrides so that I can compile ?
It would probably be best to just use your own fork for the moment. :thinkies:
Because if you're going to use it, you'll want to be able to patch the many broken things with it, and I don't want to be working on maintaining the old branches.
Haha, fair point.
Thanks for the heads up.