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

76 pass backend options on init instead of run and provide pv name formatting options #84

Closed

Conversation

evalott100
Copy link
Contributor

Closes #76

Reopening because #77 was struggling with fetching a dropped commit.

@evalott100 evalott100 changed the title 76 pass backend options on init instead of run 76 pass backend options on init instead of run and provide pv name formatting options Nov 20, 2024
@evalott100 evalott100 requested review from GDYendell and jsouter and removed request for GDYendell November 20, 2024 10:42
@GDYendell
Copy link
Contributor

I would like to have the pv naming in a separate PR. I am not sure it is quite right yet and maybe we should rework the way we handle combinations of controller paths and attributes entirely. I don't like that you have to call _convert_attribute_name_to_pv_name with an is_attribute flag.

Also, I don't think we need CAPITALIZED_CONTROLLER_PASCAL_ATTRIBUTE and it seems to be complicating the logic here a lot. I think what need need is for capitalised acronyms to be left alone regardless of the mode, e.g. FP in controller path or PVI as the leaf. PascalCase doesn't handle acronyms explicitly, but I think we should add some handling around that.

@evalott100 evalott100 closed this Nov 20, 2024
@evalott100 evalott100 deleted the 76-pass-backend-options-on-init-instead-of-run branch November 20, 2024 13:40
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

Successfully merging this pull request may close these issues.

Pass backend options on init instead of run
2 participants