Skip to content

Grammar issue when arch option is incorrect #173

@Sebastian-Webster

Description

@Sebastian-Webster

Very small bug - When you use an incorrect arch for the arch option, there is a comma after the last correct arch.

This is because the allowedArches array has undefined as its last item, so the join method is adding a comma after the last arch. The fix is to move the undefined check out of the allowedArches.includes() check.

Metadata

Metadata

Labels

bugSomething isn't working

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions