dotCMS / dotCMS/core

[EPIC] UVE: Stable Release & Enhancements

Open
#31,697 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Team : Scout
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Overview

This sub-epic aims to enhance UVE by supporting the GraphQL API and Page API, enabling page editing based on user selections. Additionally, it addresses various mirror errors related to iframe behavior.

Goals

  1. UVE detection works reliably in all environments
  2. No memory leaks in long-running sessions
  3. Establish UVE detection (server/client)

[!IMPORTANT]
EACH CHANGE SHOULD BE DOCUMENTED IN THIS DOC TO HELP US DESIGN A MIGRATION GUIDE
UVE & SDK IMPROVEMENTS: MIGRATION DOC

[!WARNING]
BEFORE DEFINING ANYTHING IN THE PUBLIC API, PLEASE REVIEW THE NAMING CONVENTION RULES: SDK Rules and Recommendations.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the UVE goals, including GraphQL API and Page API support, server/client detection, iframe mirror errors, and memory-leak prevention. Use the linked UVE & SDK Improvements migration document and SDK Rules and Recommendations as context; done should satisfy the stated goals and document each change for migration planning.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql, java
Domain
api, backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.