feat: initiative work items, nullable work item updates, rich text values, and property enums - #58
Merged
Merged
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (18)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Records the new v1 exports (initiative work items, rich text value types, CustomerRelationType), the reshaped property/customer/update types, and v2's CustomerPropertyType moving to the V2CustomerPropertyType alias. Co-Authored-By: WOZCODE <contact@withwoz.com>
Prashant-Surya
approved these changes
Sep 22, 2026
This file contains hidden or 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
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.
Description
1. Initiative work items
New
client.initiatives.workItems(list,add,remove) against/work-items/. It accepts any work item type.listpages by cursor (per_page,cursor)client.initiatives.epicsmarked@deprecated; it still works2. Clearing fields on update
UpdateWorkItemtyped dates asstring, sonulldidn't compile.undefinedis dropped from the request, so there was no way to clear a field.start_date,target_date,parent,estimate_pointare nowstring | nullnullclears the field; a field left out is untouched3. Rich text property values
Plane requires rich text as an object. A bare string returns
400 "Rich text value must be an object".RichTextValue { description_html }— requestWorkItemPropertyValueDetail/RichTextValueDetail— response; the HTML is invalue_detailvalues.retrieve/create/updatenow returnWorkItemPropertyValueDetail | WorkItemPropertyValueDetail[]. The previous type was thelistendpoint's shape, which these endpoints never return.4. Property enums
PropertyTypeURL,EMAIL,FILE,FORMULA,CASCADINGPropertyRelationTypeRELEASE,RICH_TEXTCustomerPropertyTypeFORMULA/CASCADINGCustomerRelationTypeISSUE,USERCustomer models use the customer types, so values Plane rejects on a customer austomerPropertyType
is exported from the root asV2CustomerPropertyType` toavoid a name clash; the types-bundle snapshot is updated.Type of Change
Test Scenarios
Offline (no Plane instance needed)
update-payload.test.ts—nullis sent; fields left out orundefinedareeps the otherinitiative-work-items.test.ts— URLs, request bodies and paging params; `/erich-text-values.test.ts— rich text is sent as an object; other value typemvalue_detailproperty-types.test.ts— compile-time checks for the customer vs. work item enumsLive
nullclears, and the other date is keptSummary by CodeRabbit
New Features
null.Deprecations
Chores