Managing code components in library

This is blocked on ✨ HTTP API for code component config entities Active , which itself is blocked on ✨ Config entity for storing code components Active .

Up until now, the XB team has been following a pseudo-scrum/pseudo-kanban process, but we're now shifting into more conventional scrum. We started a new 2-week sprint last Thursday (Jan 16). I'm tagging our current sprint's issues for visibility.

The UI updates I worked on so far to prepare the sidebar are all useful outside of code components, too. I extracted those changes to ✨ Update appearance items listed under "Library" and "Layers" Active .

✨ Config entity for storing code components Active is in, so decrementing how many issues this is blocked on.

✨ HTTP API for code component config entities Active is in, we can drive this one home!

balintbrews → credited jessebaker → .

Crediting @jessebaker for great code review comments.

I addressed all comments and polished the code editor styling to match the overall design language we're introducing with the dialog etc.

Automatically closed - issue fixed for 2 weeks with no activity.

Found an issue with adding a new component whilst testing ✨ Loading and auto-saving an edited code component Active and went to expand the e2e to allow for it.
But found we didn't add any here 🙊