feat: dasc #181 handle arrays, #196 annotate based on schema

[kozmaadrian]

While working on #181, we realised that we need to modify a core part of the annotation mechanism described in #196.

• Ticket: [dasc] Ability to add & remove array items in the UI #181
• Ticket: [dasc] Persist Only Required Fields, Schema Defaults, and User Data #196

The refactored annotation mechanism depends on the changes introduced in #181 to properly test both the UI behavior and data persistence.

The updates are split across two separate PRs:

• Ticket: 181 -> PR feat: Implement add action for array items. #190
• Ticket: 196 -> PR feat: Make annotations rely on schema first. #197 (built on top of PR 190

The current PR is intended to provide a clearer view of all changes compared to the main branch.

Demo:

demo-pr-198.mov

[aem-code-sync]

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
In case there are problems, just click a checkbox below to rerun the respective action.

• Re-run PSI checks
• Re-sync branch

Commits

• b12713e ✅ (latest)
• 6293a4b ✅
• 131f4bf ✅
• a52259d ✅
• 3e14ad9 ✅
• 1f04921 ✅
• f54f121 ✅
• 6f8b9b5 ✅
• e3a1622 ✅
• 86dbcda ✅
• 3fe2da1 ✅
• 47998ba ✅
• 181f173 ✅
• f832285 ✅
• 44232dd ✅
• a63758e ✅
• efe6b5c ❌
• 755a263 ❌
• 95b6ef8 ❌
• 4446ca6 ❌
• 6557a17 ❌
• 219e23b ❌
• 8540b28 ❌
• 71e41a4 ❌
• d89e16c ❌
• 6e6f6cc ❌
• 77c647a ❌
• 3976f26 ❌
• 12beeba ❌

[kozmaadrian]

Since we are not enforcing any values yet, a general non-selectable (disabled) option is added to ensure the UI displays a clear and informative value.

[kozmaadrian]

As agreed, boolean fields must default to false as a fallback value.

[auniverseaway]

@kozmaadrian @mhaack at a high level this looks OK to me. Certainly fine to unblock us and move to the schema-first approach. If I start digesting the code more and have issues, I can raise PRs.

@chrischrischris would you mind give this a quick glance? I want to make sure we have SMEs available in US time zone to be able to support this feature. I can give a lot more context when needed.

[kozmaadrian]

@mhaack @chrischrischris @auniverseaway

I’ve applied the requested small change to the PR. Could one of you please help and merge it when you have a moment?

[hannessolo]

I figured out how to make it run, but found some issues.

• Boolean values don't seem to work, the check box appears but doesn't add a value to the json output
• For some reason the UI isn't displaying the property names
• The navigation is completely empty

But maybe I just didn't set it up correctly, if you have a template I can copy instead of my from-scratch setup here that might help.

I used

https://da.live/formsref?nx=local#/hannessolo/da-playground/formstest
https://da.live/apps/schema#/hannessolo/da-playground

[mhaack]

The boolean might be related to the storage, only "true" is stored. This is fixed by #201

The other two issues are new to me.

[hannessolo]

Boolean values don't seem to work, the check box appears but doesn't add a value to the json output

Now fixed

For some reason the UI isn't displaying the property names

I was missing the title property in the schema

The navigation is completely empty

Same, title missing

[hannessolo]

I tested it and it looks fine to me to get the core functionality in, as @auniverseaway commented we can always refactor things in a new PR if there's things we don't like.