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
Proposal:
Require a min or a max y axis domain for a graph, instead of min and max.
Current behavior:
There needs to be a min and max when using a custom y axis domain
Desired behavior:
Require only one of the two and set the other one automatically.
Alternatives considered:
None
Use case:
There are many use cases where it is good to start/end a graph at a certain point. For example when displaying latency (ping), the graph should always start at 0, but the end shall vary accordingly to the highest latency
The text was updated successfully, but these errors were encountered:
Proposal:
Require a min or a max y axis domain for a graph, instead of min and max.
Current behavior:
There needs to be a min and max when using a custom y axis domain
Desired behavior:
Require only one of the two and set the other one automatically.
Alternatives considered:
None
Use case:
There are many use cases where it is good to start/end a graph at a certain point. For example when displaying latency (ping), the graph should always start at 0, but the end shall vary accordingly to the highest latency
The text was updated successfully, but these errors were encountered: