[dannyleech]

Resolves #616

Moves every plugin and provider out of plugins/beta/ and providers/beta/ so they share one flat layout, and deletes the old draw-ml and draw-ol plugins, which plugins/draw replaces. Apart from removing the draw-ml and draw-ol code, nothing behaves differently.

Changes (196 files)

• 95 moved: draw-es, frame, map-styles, scale-bar and use-location to plugins/, and esri, open-names and openlayers to providers/. 77 are unchanged; 18 only need one less ../ in their relative imports.
• 71 deleted: plugins/beta/draw-ml and plugins/beta/draw-ol.
• 30 edited to use the new paths:
  • build, test and Sonar config, and govuk-prototype-kit.config.json
  • the demos and the style switcher template
  • tests in datasets and draw that import from providers/openlayers
  • the architecture diagram

Things to note

• ESM import paths don't change, except that @defra/interactive-map/plugins/draw-ml is removed. Use /plugins/draw instead.
• Files that were under plugins/beta/ and providers/beta/ inside the package have moved up a level. Anyone loading them by their location, such as GOV.UK Prototype Kit templates using /plugin-assets/.../plugins/beta/... or UMD copy scripts, needs to remove beta/ from those paths.
• The farming demo now uses plugins/draw instead of draw-ml.
• Folders that aren't stable yet are still excluded from coverage and Sonar, now listed by name, so Make the map styles plugin stable: unit tests, fixes and docs #460, Make the scale bar plugin stable: complete unit tests and fixes #461 and Make the frame plugin stable: unit tests, fixes and docs #462 can each remove their own.
• No docs pages needed updating. The UMD and CSS steps tell consumers to copy a plugin's files from plugins/<name>/dist/, but for map-styles and scale-bar those files were under plugins/beta/<name>/dist/ inside the package. They're now where the docs say.

Testing

• ESM and UMD builds pass, and every package export, Prototype Kit asset folder and template asset points to a file that exists
• Tests pass with 100% coverage, and lint passes
• Every demo compiles, and the docs site builds

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud