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

Not recognized commands in config files should give errors #204

Open
zuckerruebe opened this issue Aug 21, 2024 · 0 comments
Open

Not recognized commands in config files should give errors #204

zuckerruebe opened this issue Aug 21, 2024 · 0 comments

Comments

@zuckerruebe
Copy link
Contributor

If I have something like

assign "..\path\to\file.csv" unitProfile

in a run.config, pytrnsys should tell me that it doesn't recognize the "assign" and refuse to continue. Currently, it just ignores it and I have no idea why the assign didn't work.

OK, we could be having a discussion about whether commands in config files should be case-insensitive, but there is the general problem that unrecognized commands/keywords in config files are just silently swallowed (a line like "foo bar baz" will just go through without pytrnsys complaining). That needs to be fixed. If that's fixed, case-sensitivity of recognized keywords becomes a non-issue, because the user will get a nice error message if they get the casing wrong.

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

1 participant