[FIX] Allow different text cases on component create #1454
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
⚡ PowerGrid - Pull Request
Welcome and thank you for your interest in contributing to our project!. You must use this template to submit a Pull Request or it will not be accepted.
Motivation
Description
This Pull Request changes the
powergrid:create
command, keeping the text case informed by the user unaltered, while still trying to normalize and prevent mistakes. Before, we tried to fix/standardize the component paths, thus preventing user errors.With this PR, we also disable the possibility to create components with dashes or underscores in the name. While PSR-4 cna can resolve underscores in namespaces, this is not very "Laravel like" and users are welcome to rename their folders and namespaces as they want, after the component is created.
When using special characters:
Will result in:
Related Issue(s): #1450.
Documentation
This PR requires Documentation update?