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.

Sign up for GitHub

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

Jump to bottom

Make variable name style consistent and safe. #408

Open
kaladay opened this issue Feb 11, 2025 · 0 comments · May be fixed by #409
Open

Make variable name style consistent and safe. #408

kaladay opened this issue Feb 11, 2025 · 0 comments · May be fixed by #409
Labels
tech debt When development teams take actions to expedite a deliverable.

Comments

@kaladay
Copy link
Contributor

kaladay commented Feb 11, 2025 •
edited
Loading

Remove the non-word-characters, such as the dash -, from the variable names.

These have found to be problematic when in Camunda and cannot be safely used.
However, the build time has no such problems.

Having a different structure for the build time and the runtime/camundatime variables is rather confusing and inconsistent.

This is a proposal to make all of the variables to be camel case.

Proposal PR is here: #409
@kaladay kaladay added the tech debt When development teams take actions to expedite a deliverable. label Feb 11, 2025
@kaladay kaladay added this to FOLIO Feb 11, 2025
@github-project-automation github-project-automation bot moved this to 📋 Backlog in FOLIO Feb 11, 2025
@kaladay kaladay linked a pull request Feb 11, 2025 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
tech debt When development teams take actions to expedite a deliverable.
Projects
FOLIO
Status: 📋 Backlog
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Issue 408: Mass update variables, ensuring camel case styling. TAMULib/fw-registry
1 participant
@kaladay