nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Uncompressed/Obfuscated version of JavaScript API for developers

ChristopherRusanowski

A lot of time when errors are generated because you passed the wrong value, or something changed between versions of the JavaScript API, the error is buried somewhere in DOJO or ESRI code that is practically meaningless. Something _a is undefined...

That makes it very difficult for debugging. While the error might be in our code, we can't determine that without trial and error to see what causes the underlying error.

If ESRI hosted (maybe in beta with and NDA or something) a version of the JavaScript API that was not compressed and obfuscated, we could determine what was causing the error easier. This would also allow people external to ESRI to debug the ESRI code and help make things better.

Encuentra más publicaciones etiquetadas con

Status: Abrir

Comentarios

FredSpataro

I would also like to see this, especially for the widgets. These controls can sometimes be very difficult to work with as you add more complex user interactions

SimonSpeich

totally agree, really a pain in the...

RyanMuller

Even if just the dojo part of it was uncompressed that would be great.

Únete a la Conversación

Inicia sesión para publicar, seguir contenido y más. ¿Nuevo aquí? Regístrate gratis.