-
-
Notifications
You must be signed in to change notification settings - Fork 102
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
Apply backend naming convention #134
Apply backend naming convention #134
Conversation
Argh, sorry, I've made a mistake...forgot about it in our discussion that name already exists as descriptive name like here. These usually contain spaces and are long, what is painful for CLI usage. I think it's easier for backwards compatibility to use another class variable name identifier for this purpose. Can you change this? Can you further add a test for the backend name generation? Anyways...great contribution, I've already removed it from my todo list 😁 |
Show a warning when a duplicate backend name (unnamed backend) is found
fd9a269
to
ba586ad
Compare
Great, thanks a lot! |
Related to #110: #110 (comment)