You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I just started using the latest version in beta and I noticed Settings > Transitive > rounds, which was cryptic without reading the docs.
Describe the solution you'd like
We should use a better choice of words and better UI. How about visibility with a dropdown for disabled, explicit only, and implicit and explicit. We wouldn't even have to change how we save the value (0, 1, or 2).
The text was updated successfully, but these errors were encountered:
@mProjectsCode I like this suggestion. We can keep the rounds as an implementation detail, but perhaps only give the choice of the 3 options above. Maybe if someone asks for it, there can be an "advanced" feature to set rounds explicitly
implicit and explicit does not relate to 2 though, it relates to potentially very many, not sure about the exact bound but an upper bound should be node_count * rule_count, of rounds.
I was thinking we could use some high-enough value for 2. Like currently, all implied rules are set to rounds: 10 by default. We can push it higher, but I think nodes * rules is practically too high
Is your feature request related to a problem? Please describe.
I just started using the latest version in beta and I noticed Settings > Transitive > rounds, which was cryptic without reading the docs.
Describe the solution you'd like
We should use a better choice of words and better UI. How about
visibility
with a dropdown fordisabled
,explicit only
, andimplicit and explicit
. We wouldn't even have to change how we save the value (0, 1, or 2).The text was updated successfully, but these errors were encountered: