fix(Editor) Cursor Inconsistency and edit lost fix in monaco editor

[nitro56565]

Closes #91

Description

The Monaco editor were experiencing cursor jumping issues and edit lost when updating state using Zustand. The cursor would jump to the top or bottom of the editor, causing a poor user experience. This issue was identified as a result of state updates causing unnecessary re-renders.

Solution

• To resolve this, I implemented immediate state management for the editor components, separating the state used for rendering the editor (editorValue, editorModelCto, and editorAgreementData) from the state used for processing updates . By updating the rendering state immediately and debouncing the processing state updates, I was able to stop the unnecessary re-rendering that made the cursor jump around all over the place.

Changes Made (TemplateMarkdown, TemplateModel and AgreementData)

• Replaced direct state updates with immediate state updates in all the three editor components.
• Implemented debounced updates for all three editors to avoid performance issues.

Related Issues

• Issue #91
• Pull Request #95

Author Checklist

• [x] Ensure you provide a DCO sign-off for your commits using the --signoff option of git commit.
• [ ] Vital features and changes captured in unit and/or integration tests
• [x] Commits messages follow AP format
• [ ] Extend the documentation, if necessary
• [ ] Merging to main from fork:branchname

[netlify[bot]]

✅ Deploy Preview for ap-template-playground ready!

Name	Link
🔨 Latest commit	915101b6d633268724f079207d4f198b30722c5f
🔍 Latest deploy log	https://app.netlify.com/sites/ap-template-playground/deploys/66ad2f3d56f2d900086b4008
😎 Deploy Preview	https://deploy-preview-95--ap-template-playground.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[nitro56565]

@dselman can you please review the code