Consistent expression validation between UI and deployment compiler

What is a one sentence summary of your feature request?

Ensure that the UI performs the same expression validation checks as the deployment/import compiler and displays all resulting warnings.

Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.

When creating or editing expressions in the Usercube UI, the system validates the expression and reports any detected issues. However, additional validation checks appear to be executed during configuration deployment.

For example, an expression created in the UI may be accepted without warnings, but when the same expression is exported to XML and redeployed, the deployment process reports warnings such as:
warning CS8602: Dereference of a possibly null reference.

This creates an inconsistency between the UI experience and the deployment experience. Administrators may believe an expression is fully valid because no warning is shown in the UI, only to encounter additional warnings later during deployment.

It would be beneficial if the UI used the same validation engine and rules as the deployment compiler, or at least displayed the same warnings that would be generated during deployment. This would allow issues to be identified and corrected earlier in the configuration lifecycle.

How do you currently solve the challenges you have by not having this feature?

Currently, we only discover these additional warnings after exporting and deploying the configuration. This requires additional testing cycles and investigation to determine why warnings appear during deployment even though the expression was accepted by the UI. We must manually review and adjust expressions after deployment feedback rather than receiving the information at design time.