-
-
Notifications
You must be signed in to change notification settings - Fork 265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
💡 allow embedding avo tables #2015
Comments
Hei @yshmarov! Great idea! Actually this is already one of our roadmap items for v3 |
Amazing! I will be looking forward! 🥰 |
This issue has been marked as stale because there was no activity for the past 15 days. |
This issue has been marked as stale because there was no activity for the past 15 days. |
Closing this because there was no activity for the past 15 days. Feel free to reopen if new information pops up ✌️ |
+1 - this would be really great to have! |
+1 - and FYI it looks like this ticket was reopened but is still marked as |
Moved it back into To-do. What is your use-case? How yould you use this feature @zlailari? |
We have 3 user types:
Being able to embed avo tables in the enterprise dashboard (for group 3) would accelerate how quickly we could ship some features |
I see. Yes, that makes sense. Would you be open to pay an enterprise license for a feature like that ($30K+/year)? |
Unfortunately, an enterprise license isn't within our budget and our current use case doesn't justify that level of expenditure. It would be a great addition to the product though! |
Yes. I agree. It would be a good feature. Can I ask what are you building with Avo? |
This should work for all resources type including the array resources. |
Feature
Maybe just by wrapping index tables into a
<%= turbo_frame_tag resource_name do ...%>
, we can render them in the views of the main app like:Current workarounds
Screenshots or screen recordings
Additional context
The text was updated successfully, but these errors were encountered: