-
Notifications
You must be signed in to change notification settings - Fork 20
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
💡 [Feature]: Create one task for bundle & package each #386
Labels
⭐ enhancement
New feature or request
💪 good first issue
Good for newcomers
👨💻work in progress
I am working on it
Milestone
Comments
Thanks @nicodecleyre for another awesome suggestion. |
Hey @nicodecleyre & @Adam-it Let me take this 🥇 Thanks, |
Sure thing 👍 |
1 task
1 task
Adam-it
pushed a commit
that referenced
this issue
Feb 3, 2025
## 🎯 Aim Currently there are 2 tasks for bundle & package each. Namely: Bundle (local) Bundle (production) for the bundle task, and: Package (local) Package (production) With this, We achieve to create one task for bundle project. When clicked on `Bundle project`, a prompt is shown with options `local` and `production`. Depending on the user selection, the command is executed in the terminal. ## 📷 Result for Bundle task Below is for local, executing `gulp bundle`  Below is for production, executing `gulp bundle --ship`  ## 📷 Result for Package task Below is for both Package local and package production, executing `gulp package-solution` & `gulp package-solution --ship`  ## ✅ What was done Added a two new methods in `TerminalCommandExecuter` with name `bundleProject` & `packageProject`, which will execute this. <img width="511" alt="image" src="https://github.com/user-attachments/assets/763694f3-3783-4f52-b800-b6526da698e4" /> ## 🔗 Related issue > each PR should be linked with a related issue [Remove this line] Closes: #386
I merged the PR. This should be part of a new pre-release shortly |
Adam-it
pushed a commit
that referenced
this issue
Feb 4, 2025
## 🎯 Aim Currently there are 2 tasks for bundle & package each. Namely: Bundle (local) Bundle (production) for the bundle task, and: Package (local) Package (production) With this, We achieve to create one task for bundle project. When clicked on `Bundle project`, a prompt is shown with options `local` and `production`. Depending on the user selection, the command is executed in the terminal. ## 📷 Result for Bundle task Below is for local, executing `gulp bundle`  Below is for production, executing `gulp bundle --ship`  ## 📷 Result for Package task Below is for both Package local and package production, executing `gulp package-solution` & `gulp package-solution --ship`  ## ✅ What was done Added a two new methods in `TerminalCommandExecuter` with name `bundleProject` & `packageProject`, which will execute this. <img width="511" alt="image" src="https://github.com/user-attachments/assets/763694f3-3783-4f52-b800-b6526da698e4" /> ## 🔗 Related issue > each PR should be linked with a related issue [Remove this line] Closes: #386
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
⭐ enhancement
New feature or request
💪 good first issue
Good for newcomers
👨💻work in progress
I am working on it
🎯 Aim of the feature
Currently there are 2 tasks for bundle & package each. Namely:
for the bundle task, and:
let's simplify this and create a single bundle task and a single package task. For both a prompt should first be shown asking if you want to bundle/package to your local environment or a production environment.
📷 Images (if possible) with expected result
🤔 Additional remarks or comments
No response
The text was updated successfully, but these errors were encountered: