Skip to content
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: change introduction to field type Text Editor on Appointment Letter && Appointment Letter Template #824

Closed

Conversation

Lucky-Tsuma
Copy link
Contributor

@Lucky-Tsuma Lucky-Tsuma commented Aug 28, 2023

The introduction field on Appointment Letter and Appointment Letter Template a data field type providing no styling options.

Previously:
image

After change:
image

Closes: #774

…`Appointment Letter Template`

change datatype from `Data` to `Text Editor` to provide more editing options
hrms.patches.v14_0.create_vehicle_service_item
hrms.patches.v14_0.change_appointment_letter_introduction_to_texteditor #28th August 2023
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You just need to change field type by editing the doctype directly. Patch isn't required here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok. This happens for standard fields though.
image

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ohh okay. Actually, both the field types create a longtext column in DB. So this transition should be allowed IG.
Description is a Text Editor field. Introduction is Long Text

image

But the quill editor adds a div enclosing the content. Maybe that's why the transition is not allowed.

image

Will have to check the framework. Closing this for now. Adding a patch won't help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants