Adjust generated scenarios

[Turbo87]

As mentioned in #3 there are some situations where it would be useful to adjust the list of generated scenarios afterwards by e.g. adding or overwriting certain dependencies or even cloning generated scenarios.

Instead of implicitly generating the scenarios when useVersionCompatibility is used I would suggest to explicitly require('ember-try-config') and then put something like scenarios: generateScenarios() in your config/ember-try.js file.

That way the generateScenarios() result could be written into a temporary variable if needed and then adjusted afterwards.

/cc @rwjblue @kategengler

[rwjblue]

Agreed.

[Turbo87]

@rwjblue I just noticed an issue with this proposal which unfortunately makes it a little harder to backport: the generateScenarios() function would have to be async and I don't think ember-try is able to handle async yet... 🤔

[kategengler]

That seems fine to me, so long as the use of versionCompatibility in the package.json stays (I still have an outside hope of using that to get addons to declare their compatibility).

[Turbo87]

@kategengler yes, I'm fine with that. the default of generateScenarios() would be to look at the package.json file for versionCompatibility unless specified otherwise.

[locks]

Is this still relevant?

[kategengler]

Yes, discussion of a similar solution is ongoing, including here: #192 (comment)