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; } } }

Custom Widget Version Control Best Practices

LTS_DSolari

I'm getting started with custom widget development and I want to make sure I'm handling my source data as best as possible:

For a single organization, should I do a monorepo or one repository per widget?
At what folder "level" do I create the repository? I assume for multi-repository workflows each widget folder is a repository but how high up should you go for a monorepo?
The docs mention a "shared-code" directory that isn't compiled into a widget but can hold common code for all widgets. Is it a good idea to use that or to create standard node packages and load them as standard dependencies? Does this change depending on how you structure the repositories?

Encuentra más publicaciones etiquetadas con

Custom Widgets

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate para una cuenta gratuita.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.