You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a developer, it's essential to maintain descriptive and explicit scripts for better understanding, especially for new team members. However, dealing with lengthy and explicit terminal commands can become tedious. To address this, there's a need to shorten the commands while preserving clarity.
Current Workaround
build_runner:
build: flutter packages run build_runner build --delete-conflicting-outputswatch: flutter package run build_runner watch --delete-conflicting-outputsbr:
b: $build_runner:buildw: $build_runner:watch
Proposal
I propose introducing an 'aliases' feature for each command, providing a more concise representation.
build_runner:
(aliases):
- br
- runnerbuild:
(scripts): flutter packages run build_runner build --delete-conflicting-outputs(aliases): bwatch:
(scripts): flutter package run build_runner watch --delete-conflicting-outputs(aliases): w
Alt Proposal
Here is an alternate approach that could be taken. It might make it easier for adoption since this approach is easier to read. However, it might be more difficult to implement as some pattern matching and parsing would be necessary
build_runner(br,runner): # multiple aliases are comma separatedbuild(b): flutter packages run build_runner build --delete-conflicting-outputswatch(w): flutter package run build_runner watch --delete-conflicting-outputs
The text was updated successfully, but these errors were encountered:
Description
As a developer, it's essential to maintain descriptive and explicit scripts for better understanding, especially for new team members. However, dealing with lengthy and explicit terminal commands can become tedious. To address this, there's a need to shorten the commands while preserving clarity.
Current Workaround
Proposal
I propose introducing an 'aliases' feature for each command, providing a more concise representation.
Alt Proposal
Here is an alternate approach that could be taken. It might make it easier for adoption since this approach is easier to read. However, it might be more difficult to implement as some pattern matching and parsing would be necessary
The text was updated successfully, but these errors were encountered: