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

Add a new mandatory CLI flag that states source code information #2543

Open
wagnerand opened this issue Oct 31, 2022 · 4 comments
Open

Add a new mandatory CLI flag that states source code information #2543

wagnerand opened this issue Oct 31, 2022 · 4 comments

Comments

@wagnerand
Copy link
Member

Is this a feature request or a bug?

Feature request

What is the current behavior?

A common issue with API submissions is that the add-on itself uses machine-generated code but developers do not attach source code to it. Some don't know, others forgot or don't do it for other reasons.

What is the expected or desired behavior?

To help reviewers and reduce back and forth with developers, web-ext should add a mandatory CLI flag that allows to pass a source code zip file and a different one to state that source code is not needed. The developer hub already does this, and the API should have a similar feature.

@eviljeff
Copy link
Member

web-ext currently works by zipping --source-dir first and uploading that so we should consider how another source directory would work in that workflow. If it's machine-generated code that it's very likely that web-ext is used in some kind of script, so perhaps specifying another directory that web-ext would zip up too would be more appropriate.

@eviljeff
Copy link
Member

@rpl @willdurand @Rob--W can I get your thoughts on how this feature should work?

@Rob--W
Copy link
Member

Rob--W commented Jun 20, 2023

The next triage meeting to discuss this is in three weeks.

Here are my thoughts:

The option being mandatory would require a major version bump.

I would accept a zip file as parameter, and not zip directories automatically. Accepting a directory carries the risk of inadvertently uploading files that the dev didn't intend to, and would also need support for including/excluding specific files/directories. I can be convinced otherwise.

@willdurand
Copy link
Member

The option being mandatory would require a major version bump.

We are working on v8 right now, so that part won't be a problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants