-
Notifications
You must be signed in to change notification settings - Fork 11
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
Toml file badly processed if it contains table aka. section in .ini files (name in brackets []) #55
Comments
Hi George, thanks for your request! You are right, this way it would only work if your APIConfig has a field which would again be called "APIConfig", and there then a field "login_page". I would have said that this is the intended behaviour. |
Closing this issue due to inactivity. Please re-open if you still consider the current behaviour a bug. |
Hi @silvanmelchior, if I remove the it works well, but in this case the file is not a toml file, just a text file with key value pairs. The And solving this would solve the issue #14 too. One file could contain more config parts in different sections BR, |
Yes, I think it should be reopened, but only repo owner / collaborator can reopen the issue |
I flag it as a possible improvement for the documentation, so it's more obvious that the toml file acts as the root of the config class and possible sections wihtin the toml file refer to sub-configs. Please also see the test file "https://github.com/Zuehlke/ConfZ/blob/main/tests/assets/config.toml" for more options. |
Hi,
confz is very good tool, started to use right now, and found the following:
I created the following config
and the login_page value was the default one. Started to debug it and found, that Toml interpreter creates nested dicts if the file contains table [APIConfig]:
and found a call in confz.py line 50:
perhaps this is the point where the nested dict makes the issue. Unfortunately PyCharm did not show the source of super()...
so finished debugging here.
Perhaps this relates a little bit to issue #14
BR,
George
The text was updated successfully, but these errors were encountered: