You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Epic for all the planned/desired enhancements to be released alongside Dojo v7.
Note: Issue creation in progress across these
High Level Goals
Widgets to be built and tested using the Dojo CLI exclusively
Complete the Material theme
Align and improve upon API of existing widgets
Expansion of Widget library
Create high-level layout / app widgets
Use of CLI
Widgets currently use a fragmented dev toolchain. We should convert to using the dojo cli tooling consistently and ensure it has capability to build both @dojo/widgets and our user's third party component libraries.
The goal here is to create a material theme for our entire widget library. The structure for this was started in widgets 6 but not completed. The epic below links to the themes repo.
Our existing functional tests are known to be flakey and to absorb large quantities of developer time both writing and fixing them. The framework itself is well tested across a range of browsers so there is little need to do this here also. We should ensure that adequate manual testing / usable examples are created when widgets are worked on.
This will be partly hangovers that did not get fully completed for dojo-6.0. This will make our existing widgets more compatible with the base / reusability direction we intend to take for dojo-7.0.
We have several overloaded widgets; checkbox, text-input, select etc. We should split them into smaller more focused widgets that work with a common base. The following list may not be extensive:
Creating new base widgets will give us a larger library to build more complex widgets on top of. This will help bulk out our offering and fill in the gaps required to build applications.
These widgets will use our existing base widgets to create highly re-usable and effecting application building blocks. These will be highly opinionated but fully themeable.
Widgets 7 Plan
Epic for all the planned/desired enhancements to be released alongside Dojo v7.
Note: Issue creation in progress across these
High Level Goals
Use of CLI
Widgets currently use a fragmented dev toolchain. We should convert to using the dojo cli tooling consistently and ensure it has capability to build both
@dojo/widgets
and our user's third party component libraries.Theme
The goal here is to create a material theme for our entire widget library. The structure for this was started in widgets 6 but not completed. The epic below links to the themes repo.
Example / Test changes
Our existing functional tests are known to be flakey and to absorb large quantities of developer time both writing and fixing them. The framework itself is well tested across a range of browsers so there is little need to do this here also. We should ensure that adequate manual testing / usable examples are created when widgets are worked on.
Existing widget improvements
This will be partly hangovers that did not get fully completed for dojo-6.0. This will make our existing widgets more compatible with the base / reusability direction we intend to take for dojo-7.0.
onValue
/value
/onKey
apisinvalid
->valid
propertieshelperText
where appropriatecustom validator helpersSplit apart existing generic widgets
We have several overloaded widgets; checkbox, text-input, select etc. We should split them into smaller more focused widgets that work with a common base. The following list may not be extensive:
New Base Widgets
Creating new base widgets will give us a larger library to build more complex widgets on top of. This will help bulk out our offering and fill in the gaps required to build applications.
ListItemNew Composite / Layout widgets
These widgets will use our existing base widgets to create highly re-usable and effecting application building blocks. These will be highly opinionated but fully themeable.
Advice/guidelines for working on official widgets
The text was updated successfully, but these errors were encountered: