We need a script to generate the structure for new services #731
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked, waiting for further changes
bug
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
help wanted
invalid
low priority
needs input
needs review
project documentation
question
research
reviewed
script
security
SQL
style
testing
topLevel
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#731
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
After the update to Service structure we should implement a script to automatically create the "skeleton" of a new service. This should be done to standardize the creation of services.
What should be done
Its definitely possible, but before starting I just want some things more clear:
Also, what is If possible verify that the name follows the naming standard? Naming standard of what exactly?
The current script creates all files (at least for Windows) but a problem right now is the use of capitalization in C#. The folder structure we are using is camelCase, but C# wants all of it's things to use Pascal. Batch does not have a function to capitalize letters.
Some suggestions to solve this is to just not use camelCase, write a custom functions to do this manually, or use a program/extensions that allows this. Bash does not have this issue
Good insight! As this was meant as a "quality of life" implementation to help in the creation of future services and not something factually necessary, makes it feel wrong to change our current standard just to implement it. I would say if we can't use the script to do it then we just make a detailed wiki of how a service should be implemented.
If we can do it with an custom fuction(no extentions) then it would be fine, but if the issue gets to complex then just go the wiki route.
Agreed, we shouldn't change existing stuff (it's too late for that anyway). I can definitely make something of my own that conforms to the Wiki and is Windows specific, just wanted to check what the leaders thought about this.