updated create_work_item to support markdown format in large text fields #261
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.
Updated
create_work_item
to accept aformat
param so that you can set large text fields to use markdown. By default it is HTML. Also note, there is not good way on create to know if the field is a large text field or not. So it is going to assume the LLM knows what you ared doing based on your prompt. As a secondary check, we are looking at the value and if it is greater than 50 characters, it is safer to assume it is a large text field. Worse case, the opp will fail if you try and set a field to markdown that is not large text.Updated
update_work_items_batch
as well to take formatGitHub issue number #218 #264
Associated Risks
Should be fine, no risks
✅ PR Checklist
🧪 How did you test it?
updated tests and ran thru manual tests