Skip to content
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

Migrate ignite packager #762

Open
joshuayoes opened this issue Aug 10, 2022 · 0 comments
Open

Migrate ignite packager #762

joshuayoes opened this issue Aug 10, 2022 · 0 comments
Assignees

Comments

@joshuayoes
Copy link

joshuayoes commented Aug 10, 2022

Note that Gluegun is community-supported and the core team will not be adding new features other than those submitted as PRs by the community.

Is your feature request related to a problem? Please describe.
Packager has a pretty limited API, Ignite has a more robust API built in that would have a better home in gluegun.

Describe the solution you'd like
An MR has been started in ignite with a new mental model for working with packager commands that would be good for porting the existing logic in ignite over to gluegun

Describe alternatives you've considered

  • We could just copy and paste the existing logic. Not a bad idea, but porting to a mental model where commands are an array of strings would be a more resilient mental model

Additional context
Prompted by this issue in Ignite where an error occured because an unexpected warning was prepended to a json payload.

@joshuayoes joshuayoes self-assigned this Aug 10, 2022
@joshuayoes joshuayoes changed the title Add a packager tool Migrate ignite packager Aug 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant