If jimu/dijit... is based on an API with no documentation how are we supposed to use it other than fumble around and then be told that we are customizing things and there is little or no support for it.
What's frustrating is that Esri does provide some documentation on a few of the classes in the API, but it's nowhere near complete. What is their rationale for doing such a half-assed job?
Michael, The jimu.js library is not an API that is going to be documented. The dijits in the jimu.js can be used by developers but there is no promise of documentation as a full API would have. The way you learn to use the dijits in the jimu libaray is to look how they are used in OTB widgets that come with WAB.
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
