New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(history): display new and unknown fields #20039
Conversation
packages/core/content-manager/admin/src/pages/EditView/components/InputRenderer.tsx
Outdated
Show resolved
Hide resolved
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Size Change: 0 B Total Size: 2.39 MB ℹ️ View Unchanged
|
packages/core/content-manager/admin/src/pages/EditView/components/InputRenderer.tsx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not tested yet but looks good to me :)
packages/core/content-manager/admin/src/history/components/VersionContent.tsx
Outdated
Show resolved
Hide resolved
packages/core/content-manager/admin/src/pages/EditView/components/InputRenderer.tsx
Outdated
Show resolved
Hide resolved
packages/core/content-manager/admin/src/history/components/VersionInputRenderer.tsx
Outdated
Show resolved
Hide resolved
…unknown-attributes-fe
…unknown-attributes-fe
All the QA test cases look good ✅ |
…unknown-attributes-fe
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
great job with the tests!
What does it do?
Putting this in review as a draft now since I will be off tomorrow. There is some outstanding work and I made one questionable decision that is up for discussion.
Why is it needed?
How to test it?
It should support all types including components and dynamic zones however currently for these types the value of those inputs is not displayed and they are always displayed in their empty state input. This is not caused by this PR and should be addressed in another PR.
TODO