-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dojo 2 beta 5 blog post #370
Conversation
|
||
### Improvements to using Custom Elements/Web Components | ||
|
||
TODO: Explain |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Added a decorator for the custom element descriptor, meaning that there is no requirement for a separate module any more (Add custom element decorator widget-core#792)
That's the only custom element change since beta4
|
||
### widget-core performance and memory improvements | ||
|
||
TODO: Explain, provide metrics? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These all went in for beta4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, we should update the roadmap then as this was listed for beta5
|
||
### Stores | ||
|
||
A number of refinements were made since the initial `@dojo/stores` release in Beta 4: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Stores wasn't really officially part of the beta4
release set (not tagged), perhaps we can add some more noise around this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They were featured in the beta4 blog... https://dojo.io/blog/2017/12/04/Announcing-Dojo-2-beta-4/ so I didn't want to repeat here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay but stores usability has been enhanced quite nicely, worth perhaps pointing out the typings for state and payload.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, added
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
|
||
Our collection of [Dojo 2 examples](http://github.com/dojo/examples/) were updated for beta 5. | ||
|
||
In particular, the [kitchen sink version of ToDoMVC](https://github.com/dojo/examples/blob/master/todo-mvc-kitchensink) now uses `@dojo/stores`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could potentially say our hnpwa example was accepted?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
have a link handy?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to the running application or the hnpwa website? or both?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So I looked at https://hnpwa.com/ but didn't see the Dojo app... I see it now at https://dojo-2-hnpwa-d668d.firebaseapp.com/
* [Your first Dojo 2 application](/tutorials/001_static_content/) | ||
* [Creating widgets](/tutorials/003_creating_widgets/) | ||
|
||
## New in beta 5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add a section for improvements and breaking changes in widget-core?
New:
Breaking Changes: (main one)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These have been added
|
||
Since the beta 4 release, we have made a number of improvements. The biggest changes and additions are mentioned here, with a complete list of changes | ||
|
||
### Initial re-architecture of the build system |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Worth including cli-create-theme
? maybe not in this section because it's about the build system but somewhere?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added
|
||
We are also working on additional packages which may land in time for 2.0, but more likely for a subsequent release: | ||
|
||
* `dojo/devtool` A development tool for Dojo 2 (Chrome and Firefox) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you think we should just say working on a solution for a Dojo 2 dev tool plugin and and dojo 2 powered grid? Basically the the devtool and diagnostics packages themselves are under review and somewhat in flux so although we will have a devtool, what that exactly looks like is currently unknown.
Also defo shouldn't say that these may land in time for 2.0 because that that's not going to happen :)
[skip ci]
[skip ci]
[skip ci]
Note: Not ready to land this, but an early draft
[skip ci]