Planning v2 release

[san650]

(This are some ideas and we're open to suggestions)

Main goals

• Make it easier to maintain
  • Support fewer versions of ember/ember-cli (just 3.0 and above?)
• Remove jQuery dependency
• Support for RFC268 tests (see Support RFC268 tests #357)
• Clean up API
  • New collection API (see New Collection API RFC #352, feat(collection): Exposes a new Collection API  #347 and feature(collection): Adds find and findBy array methods #345)
  • Cleanup API options, helpers, requires, etc.
• Site redesign with ember-cli-addon-docs (ember-cli-addon-docs  #353)
• Migration path from v1.14
• Dedicated deprecations page in the guide ([docs] add deprecations page #465)
• Adapters (Adapters #479)
• Embroider compatibitlity (Incompatible with Embroider 's staticAddonTestSupportTrees optimized mode #539)

Deprecations

• v1.4 will include the new collection API with deprecation warnings
• multiple selectors (group)
  • v1: deprecate
  • v2: replace deprecated code with error
• Drop page.render()
• imports from test-support Deprecate imports from test-support #368
• is Deprecate "is" helper #442
• deprecate findElement/findElementWithAssert Introduce DOM element finders #463
• deprecate url in create Deprecate url as the first create argument #464
• deprecate setContext (Deprecate setContext #448)
• deprecate multiple
• string-properties-on-definition deprecation
  • v1: deprecate
  • v2: replace deprecation with an error
• create-url-argument deprecation
  • v1: deprecate
  • v2: remove deprecated code
• update "/docs/guides". Make sure migration page is up to date

[ro0gr]

Remove jQuery dependency

I think in order to achieve that in v2, we should plan deprecations for APIs which are directly bound to jquery, like is, findElement, and probably others

[yratanov]

can I help with this?

[ro0gr]

@yratanov Thanks for the interest!

I believe there are few more things needed. I'll work to create missing tickets and update this one today.

[SergeAstapov]

@ro0gr @san650 out of curiosity, did you change plans regarding V2 or do you consider it "close to be done"?

[ro0gr]

@SergeAstapov Not sure why the issue was actually closed, maybe it is so due to majority of the tasks listed in this ticket has been done. I'm definitely interested in moving v2 release to completion. Hope to dedicate some time to continue working on it(hopefuly this year).