Skip to content
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

Ensure settings from previous render do not affect next render. #65

Open
samussiah opened this issue Jan 29, 2019 · 1 comment
Open
Assignees

Comments

@samussiah
Copy link
Contributor

After a render and then a settings change, safety-results-over-time kept adding additional None group-by options. Setting groups: null in the settings text input fixed the issue.

@samussiah samussiah added this to the v0.10.0 milestone May 13, 2019
samussiah added a commit that referenced this issue May 24, 2019
@jwildfire jwildfire modified the milestones: v0.10.0, v1.0.0 Nov 20, 2019
@jwildfire jwildfire added this to To do in v1.0.0 Nov 21, 2019
@samussiah samussiah removed this from To do in v1.0.0 Dec 3, 2019
@samussiah samussiah removed this from the v1.0.0 milestone Dec 3, 2019
@samussiah
Copy link
Contributor Author

#79 addresses this in a roundabout way, i.e. forget state maintenance, we'll render something fresh every time

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants