Repository navigation
fix(editor): leave a schema read-only field unchanged (#5345) - #5355
Merged
Merged
Conversation
Edit mode omits a content-type read-only field from the fields PUT and keeps the stored value on screen. Saving another field succeeds. Close then Cancel does not write. HTTP 400, 403, and 409 are not success. > Co-Authored by Grok Build 1.0.46 using grok-4.7 with agent night-issue-prs.
> Co-Authored by Grok Build 1.0.46 using grok-4.7 with agent night-issue-prs.
…-field > Co-Authored by Grok Build 1.0.46 using grok-4.7 with agent night-issue-prs-erlang.
Collaborator
Author
|
Erlang LGTM. In-diff bugs: 0. Recommendation: approve. Report:
|
This was referenced Oct 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Parent: #4532 (slice 82). Fixes #5345.
In EditorHost Edit, a content-type field with
readOnly: truestays on the stored value. Saving a different field succeeds. The fields PUT omits the read-only field, so a client edit is never sent. Close then Cancel does not write. HTTP 400, 403, and 409 are not success and do not change the read-only value. View mode, required-field refusals, and file/image widgets are unchanged.Operator: Grok: night-issue-prs (model grok-4.7)
Test plan
Checklist
product-docs/8.2/admin/content-explorer.md(Content Editor controls: schema read-only field)editorReadOnlySave.test.ts,EditorHost.readOnlyField.test.tsx,editorPreview.test.ts; WebUI and perc-qa-automation standaloneclean installgreenmodules/perc-qa-automation/frontend/tests/editor-host-readonly-field.spec.json QA H2final/signature change, so no reverse-dep installBuild evidence
modules_built: WebUI, modules/perc-qa-automation
downstream_checked: none (TypeScript and docs only; no Java type made final or sealed, no public/protected signature change)
No new compiler or Surefire warnings from this change. Pre-existing javadoc "no comment" warnings on PSDefaultLandingView remain.
UI proof (QA H2)
Golden smoke was not run. This change is the editor field form only, not shell chrome.
Pre-push local code review
Summary
Machine analysis found 2 finding(s), 0 bug(s).
Scope
Recommendation
approve
Gate
Issues
Issue 1 -- Severity: bug
complexity.cognitivearborist-metricshandleSavecognitive=138 (max 15), cyclomatic=172 (max 15)Issue 2 -- Severity: suggestion
llm.errorllmollama-dev-coderfailed: http: status 500 Internal Server Error body {"error":{"message":"llama-server process has terminated: exit status 1: cudaMalloc failed: out of memory\nalloc_tensor_range: failed to allocate CUDA0 buffer of size 5064192000\nerror loading model: unable to allocate CUDA0 buffer","type":"api_error","param":null,"code":null}}Erlang intent
Intent: edit mode builds the fields PUT with
fieldsForEditorSave, which omits schemareadOnlyrows and still omits file and image widgets.setField,setFile, andmarkBinaryClearignore schema read-only names. The control shows the stored value, Clear stays hidden, and a client edit is not an unsaved change. Cancel does not call save. HTTP 400, 403, and 409 stay on the error path and do not mark the item saved. ServerapplyUpdateswrites only fields present on the PUT, so an omitted read-only field keeps the stored value. ThehandleSavecognitive-complexity row is preexisting, not in-diff, and does not block. Companions present:editorReadOnlySaveVitest,EditorHost.readOnlyFieldtest, preview dirty-check test, Playwrighteditor-host-readonly-field.spec.js, andproduct-docs/8.2/admin/content-explorer.md. No new filesystem path joins. No agent rule files. Ollamadev-coderCUDA OOM is non-blocking; machine findings kept.