https://avo.cool logo
Join Discord
Powered by
# avo-2
  • l
    probably the easiest solution here is to add 
    data: { turbo: false }
    to your forms
    Copy code
    ruby
<%= form_with url: some_path, data: { turbo: false } do |f| %>
   ...
<% end %>
  • l
    this is the "dependent fields" feature and it's not available yet
  • l
    we want to bring that on pretty soon. we know how powerful it is
  • l
    one thing you could do is let's say you have a post with a title a type (dropdown with 
    simple
    and 
    advanced
    options) and another two fields 
    simple_reason
    and 
    advanced_reason
    that you'd like to toggle based on the select field
  • l
    on the 
    New
    screen show only the title and the select field, and on the edit, show the 
    simple_reason
    or 
    advanced_reason
    based on the model value
  • b
    in the dashboards docs, under visibility, there's a reference to 
    params
    - https://docs.avohq.io/2.0/dashboards.html#dashboards-visibility what would these params be? i have users which are moderators for one or more 'systems'. i'd love to present a dashboard for performance of a system but right now it looks like i need to make duplicate dashboards and duplicate cards for each system. could those params help with this?
  • l
    Hey John, great question!
  • l
    To settle the first question, the 
    params
    are the regular request params you get in the controller when the dashboard is rendered
  • l
    regarding the second issue of duplicating cards, we fell into that trap too. Let's say you have a metric card that displays the count of Posts. If you want to show the count of featured posts then you'd need to create a different card, and so on
  • l
    we're going to improve that in the near future (two-three weeks) by allowing you to pass special options to the cards in the dashboard.
  • l
    essentially doing something like this in a dashboard file
  • l
    ofc, the API isn't settled yet. I'd like to be able to pass blocks as well. this is just pseudo-code right now👆
  • l
    does this answer your question?
  • b
    yes yes yes - that would be awesome! i assumed this was just something that would be improved over time
  • b
    the other part was around using the same dashboard for multiple different scopes
  • b
    whether that is having multiple actual dashboards, or having a select field as part of a dashboard to choose which scope to use
  • l
    yeah. we will improve that, but for now you shoud create a card for each metric 😬
  • l
    same dashboard for multiple different scopes, we haven't thought about that
  • b
    so like a 
    DiscordChannelDashboard
    and i could select one of multiple channels to show me current active users etc
  • l
    hmm... that's not a bad idea actually
  • l
    makes sense
  • l
    you could hack it for now actually
  • l
    create one dashboard. add one card with a opartial and a dropdown that redirects to the same dashbaord URL with some param attached 
    ?channel="help
    . then, pick up that param in the dashboard and show different things?
  • b
    oh cool - that's a smart approach. do cards have access to the params as well?
  • l
    ... until we create a proper solution 🙂
  • l
    you should get 
    params
    . lemme check
  • l
    you do get the params but they are actually the card params, not the dashboard params
  • l
    cards being hotwire frames, so they are different
  • l
    I'll have to push an update for that
  • b
    no worries, i probably wont get on to this for a couple of weeks. just gotta change the way my analytics stuff works at some point and dashboards would be a great option
1...323334...64Latest