feature: make axis limits for line charts explicitly nullable #1900
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
make axis limits for line charts explicitly nullable, so thy work correctly with strictly typed applications
What kind of change does this PR introduce? (check one with "x")
What is the current behavior? (You can also link to an open issue here)
When developing an application with strict null typings, axis limits can not be set to null, so they are determined automatically.
What is the new behavior?
Typing is explicitly nullable, so the API reflects that these values are optional (as the implementation already handles it).
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: