v0.2.0 was just released

Changes

• Kaffy now supports phoenix 1.4 and higher.
• The :otp_app config is now required (breaking change).
• Removed some deprecation warnings when compiling kaffy (apparently introduced some new warnings).
• Massively simplified configurations. The only required configs now are otp_app , ecto_repo , and router .
• Added a CHANGELOG file to communicate and track changes easily.
• Kaffy will now auto-detect your schemas and admin modules if they’re not set explicitly. See the README file for more. This should get me closer to my original post’s points:

Can handle as many schemas as necessary

and

Should be easy to use whether with a new project or with existing projects with a lot of schemas

Thank you for your interest. I’m getting extremely motivated to work on this project with the current response/feedback.

I’m seeing an error on the show view for a resource with an embedded struct:

Protocol.UndefinedError: protocol Phoenix.HTML.Safe not implemented for %{} of type Map. This protocol is implemented for the following type(s): Decimal, Phoenix.LiveView.Rendered, Phoenix.LiveView.Comprehension, Phoenix.LiveView.Component, Float, Time, BitString, Phoenix.HTML.Form, Atom, DateTime, NaiveDateTime, Integer, Date, List, Tuple


1
File "lib/phoenix_html/safe.ex" line 1 in Phoenix.HTML.Safe.impl_for!/1 (phoenix_html)
2
File "lib/phoenix_html/safe.ex" line 15 in Phoenix.HTML.Safe.to_iodata/1 (phoenix_html)
3
File "lib/phoenix_html.ex" line 154 in Phoenix.HTML.html_escape/1 (phoenix_html)
4
File "lib/keyword.ex" line 832 in Keyword.update!/4 (elixir)
5
File "lib/phoenix_html/form.ex" line 825 in Phoenix.HTML.Form.generic_input/4 (phoenix_html)
6
File "lib/kaffy_web/templates/resource/show.html.eex" line 8 in anonymous fn/4 in KaffyWeb.ResourceView."show.html"/1 (kaffy)
7
File "lib/enum.ex" line 2111 in Enum."-reduce/3-lists^foldl/2-0-"/3 (elixir)
8
File "lib/kaffy_web/templates/resource/show.html.eex" line 5 in KaffyWeb.ResourceView."show.html"/1 (kaffy)

On the list view it displays [object Object] for what I assume is the offending column

Thank you for reporting this. Support for embedded schemas/fields is still not there yet. There’s already an issue on GitHub though so it’s planned. If you could share some generic code here or on GitHub of what your schema looks like that would greatly help.

Thanks.

I’ll add it to the Github issue, which probably would have been the proper place to report this in the first place. Sorry, and thank you!

v0.2.1 (2020-05-10)

• [feature] Added support for embedded schemas.
• [feature] Added support for :map fields for json values.
• [enhancement] Use the json library configured for phoenix instead of hardcoding Jason.
• [bugfix] Don’t crash when the schema has a has_many or has_one association.
• [bugfix] Don’t crash when the schema has a map field or an embedded schema.

v0.3.0 (2020-05-11)

This version has a few bug fixes and a few nice additions.

Mainly:

• A much improved and much more detailed README file.
• The introduction of callbacks!

v0.3.1 (2020-05-12)

• [enhancement] A better way to handle foreign key fields with a huge amount of records to select from.
• [enhancement] Retrieve the actual name of the association field from the association struct.

This update will make things extremely easier for people who have too many records in the database.

Example:

Creating a new Comment record with a belongs_to :post, MyApp.Blog.Post association, where we have more than 20 posts. Kaffy will render the following:

Screen Shot 2020-05-12 at 06.40.22296×101 1.55 KB

Once the search button is clicked, a new window will open like the following:

Screen Shot 2020-05-12 at 06.40.42792×443 31.4 KB

Posts are paginated and searchable. Once you select a post, kaffy will populate its ID in the form and close the window:

this project looks very promising. well done @aesmail - at the moment I’m using react-admin to handle admin panel on a phoenix application, but happy to start migrating over Kaffy, will check it out soon.

Coming from Ruby 2 years ago, I really missed something similar to active admin on elixir. and Kaffy looks very similar to it

Thank you @antonioparisi !

I hope you’ll try and find kaffy useful. Please let me know if you face any issues since I’m very interested in the experience of kaffy being used in existing projects.

And you’re right. My biggest inspirations are the built-in admin from django and activeadmin from rails since I’ve been using both heavily for other projects. I’m trying to combine the best features from these two.

I’m not familiar with react-admin, but it looks awesome! If you don’t mind me asking, what do you like most about it?

I’ll try to use it for a few days and see what good ideas can be implemented in kaffy.

To be fair I’ve been kinda forced to use react-admin because of the open source availability in terms of admin panels out there at the time when I started. It offers the most reasonable approach to build something straight forward and customisable using react.
Unique big downside of it is that being detached from the APIs (phoenix app), you’ve to build your own endpoints for any action, which to be honest with you is a huge ball-ache

I’ll try Kaffy ASAP since it looks awesome so far in the Phoenix/Elixir world. I’ll give you my feedback on it as soon as I can.

Thanks so much for the amazing work you put on it so far @aesmail keep up the good work!