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 different pv naming convensions as input options #64

Open
evalott100 opened this issue Oct 17, 2024 · 1 comment
Open

Allow different pv naming convensions as input options #64

evalott100 opened this issue Oct 17, 2024 · 1 comment
Assignees

Comments

@evalott100
Copy link
Contributor

In #42

All attribute names were converted to pascal case. We should add a new options enum to pass into the ioc specifying what conversion to do, and specifying the epics seperator.

@evalott100 evalott100 self-assigned this Oct 17, 2024
@GDYendell
Copy link
Contributor

GDYendell commented Oct 22, 2024

I am happy with what you have on your branch so far, but would like either

  • sub controller node and leaf naming conventions to specified separately (e.g. caps for nodes and pascal for leaf)
  • don't convert node names at all and just use the string passed to register_sub_controller - we only need to convert the attribute names really as they have to be defined as python attribute names

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