-
Notifications
You must be signed in to change notification settings - Fork 742
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
Lucky-Tsuma
wants to merge
1
commit into
frappe:version-14-hotfix
from
Lucky-Tsuma:version-14-hotfix
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
22 changes: 22 additions & 0 deletions
22
hrms/patches/v14_0/change_appointment_letter_introduction_to_texteditor.py
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
import frappe | ||
|
||
def execute(): | ||
try: | ||
doc_types = ['Appointment Letter', 'Appointment Letter Template'] | ||
|
||
field_name = 'introduction' | ||
|
||
for doc_type in doc_types: | ||
meta = frappe.get_meta(doc_type) | ||
|
||
if field_name in [field.fieldname for field in meta.fields]: | ||
for field in meta.fields: | ||
if field.fieldname == field_name: | ||
field.fieldtype = 'Text Editor' | ||
field.save() | ||
break | ||
else: | ||
print(f"Field '{field_name}' not found in '{doc_type}' DocType.") | ||
|
||
except Exception as e: | ||
print(f"Error: {e}") |
Oops, something went wrong.
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.
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.
You just need to change field type by editing the doctype directly. Patch isn't required here.
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.
Ok. This happens for standard fields though.
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.
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
But the quill editor adds a div enclosing the content. Maybe that's why the transition is not allowed.
Will have to check the framework. Closing this for now. Adding a patch won't help.