Roadmap for 1.0.0
See original GitHub issuee-c’s been stable for a while, probably time to make it 1.0.0. Here’s some things I’d like to try and address before then (and please feel free to comment and link to important not-yet-addressed existing issues):
- Better testing solution / methodology for timer loops and slow timers, possibly involving ember-milestones
- (possibly) changing the behavior of error handling: it’s really crappy that we populate the
.error
field on the task instance AND we still bubble the error out of the run loop. Error handling is hard but it’s one of the dumber behaviors/apis in e-c- proposals/idea: Selective error bubbling
- pattern: marking error as handled, ignored in Ember.onerror
- fix waitFor* not working with race() and other promise helpers
…and many more (i think): please help me fill this out.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:17 (8 by maintainers)
Top Results From Across the Web
Version 1.0.0 Roadmap - GitHub
An open-source starter kit that will help you build full-stack multi-tenant SaaS platforms efficiently and help you focus on developing your ...
Read more >A Roadmap to 1.0 - Node-RED
If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users...
Read more >Identify roadmap to release 1.0.0 [#3285072] | Drupal.org
Help the community know which tickets to prioritize. It would be great if there was a roadmap to identify which existing or new...
Read more >Roadmap — FAIR Data Point 1.0.0 documentation
User Documentation. About FAIR Data Point. Deployment. Installation · Configuration. OpenRefine Extension. Usage · Setup. Development. Contributing; Roadmap.
Read more >Roadmap v.1.0 for Google Workspace - Sortd
Roadmap v.1.0 ... Roadmap v.1.0. Website: Roadmap v.1.0. Overview. Radically transparent project & team management app. Summary.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
+1 on error handling. I am often confused about how to use the try/catch blocks with my tasks
This is a great list, but I’d like to put a vote up for declaring 1.0 right now and addressing these as time permits possibly for 2.0 if they are breaking. Or 3.0, or 4.0 😜
Tons of apps and addons are using this in production now which points to it’s stability and the reasonableness of a 1.0 designation, but it also makes it a primary source of conflicts for us when using
ember-cli-dependency-lint
.The reason is that an addon which declares
"ember-concurrency": "^0.8.0",
needs to be updated for0.9
and0.10
, whereas declaring"ember-concurrency": "^1.0",
would allow NPM to just resolve these conflicts automatically giving the latest version in most cases.