-
Notifications
You must be signed in to change notification settings - Fork 5
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
Generate project structure using repo-config #1
Conversation
Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
"cookiecutter": { | ||
"Introduction": "", | ||
"type": "lib", | ||
"name": "client-microgrid", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting, I used frequenz-dispatch
here for the other repo. Following this logic I should have used dispatch-actor
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, just dispatch
in this case. Not sure if you used the actor
or lib
type for it, but in both cases dispatch
would have been the right choice, if it is a pure actor
repo, it will build all the names using the frequenz-actor-
prefix, for lib projects it just uses frequenz-
and I think a -python
suffix for the repo name. But this only affects the defaults, if you changed the other variables then it has no effect.
See https://frequenz-floss.github.io/frequenz-repo-config-python/v0.9/user-guide/start-a-new-project/#template-variables-reference (although I just realized there is no mention of how exactly other variables are built from this one).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did consult the reference before filling it out ;)
Still wasn't clear if I should follow a certain pattern, e.g. we have every package prefixed with frequenz-
etc
part:client
GitHub labelgrpcio