V3 fix render issue in legal documents #717
Merged
Conversation
This file contains 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
…on if it does. Also made richtext required
anemne
requested review from
christinaroise and
mathiazom
and removed request for
christinaroise
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
mathiazom
reviewed
Sep 26, 2024
Co-authored-by: Mathias Oterhals Myklebust <[email protected]>
mathiazom
approved these changes
Sep 26, 2024
christinaroise
approved these changes
Sep 27, 2024
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.
Short Description
I’ve added a check to determine if the rich text is undefined. If it is, the user will be informed that it is empty, and added a redirectbutton to the given document. Additionally, I’ve made the rich text field in the legal document required.
Visual Overview (Image/Video)