Skip to content

--no-warp-drive config when the option isn't used #271

@Windvis

Description

@Windvis

It seems that generating an app without passing any arguments adds the --no-warp-drive option to the ember-cli-update.json file which means any future updates will use the incorrect flags.

This logic seems wrong:

!options.warpDrive && `"--no-warp-drive"`,

Also, do we still want to output the --no-ember-data option? I assume we only want --no-warp-drive or no option at all at the moment?

This adds a failing test: #272

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions