The templeate folder name in the /setup directory should be spelled template.
Types of changes
What types of changes does your code introduce to the project: Put an x in the boxes that apply
[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Update docker image version of FIWARE GE.
[ ] Update only documentation, not any source code.
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code.
[x] I send this pull request to the v0.37.0-next branch.
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules
I tested the setup works as before on a fresh installation. I don't know how/where to update the changelog.
Further comments
I'm not sure, whether renaming a folder could cause issues for users, who already ran the setup. If that's the case, no problem to reject this pull request. This is just for aestetic reason. ;-)
fisuda
commented
3 months ago
Proposed changes
The
templeatefolder name in the/setupdirectory should be spelledtemplate.Types of changes
What types of changes does your code introduce to the project: Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.v0.37.0-nextbranch.I tested the setup works as before on a fresh installation. I don't know how/where to update the changelog.
Further comments
I'm not sure, whether renaming a folder could cause issues for users, who already ran the setup. If that's the case, no problem to reject this pull request. This is just for aestetic reason. ;-)