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

Allow numbers in safe filenames and report text #371

Closed
plocket opened this issue Aug 11, 2021 · 3 comments · Fixed by #382
Closed

Allow numbers in safe filenames and report text #371

plocket opened this issue Aug 11, 2021 · 3 comments · Fixed by #382
Assignees
Labels

Comments

@plocket
Copy link
Collaborator

plocket commented Aug 11, 2021

Right now, scenario names get stripped of numbers when converting them to either of the above. Avoid stripping those out as they can be quite useful.

@plocket plocket added the quick label Sep 3, 2021
@niharikasingh
Copy link
Collaborator

The main place this conversion to safe filenames happens is in getSafeScenarioFilename, and there might be a few other scattered places.

@plocket
Copy link
Collaborator Author

plocket commented Dec 31, 2021

I think this exercise has highlighted that there are a few concerns that need to be separated - the scenario id, the scenario report heading, and the scenario filename. I've made PR #463 on the current PR branch for this issue.

@plocket
Copy link
Collaborator Author

plocket commented Jan 7, 2022

Closed by #463 and #476

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

Successfully merging a pull request may close this issue.

2 participants