Skip to content

Introduce tenup-content-connect-update-relationships-order action - #115

Closed
ocean90 wants to merge 2 commits into
10up:developfrom
wearerequired:feature/tenup-content-connect-update-relationships-order
Closed

Introduce tenup-content-connect-update-relationships-order action#115
ocean90 wants to merge 2 commits into
10up:developfrom
wearerequired:feature/tenup-content-connect-update-relationships-order

Conversation

@ocean90

@ocean90 ocean90 commented Jul 2, 2025

Copy link
Copy Markdown
Contributor

Description of the Change

Introduces a new action to let extenders run logic after order has been updated.

Closes #114

How to test the Change

Changelog Entry

Added - tenup-content-connect-update-relationships-order action for developers.

Credits

Props @ocean90

Checklist:

s3rgiosan
s3rgiosan previously approved these changes Jul 2, 2025
@s3rgiosan

s3rgiosan commented Aug 14, 2026

Copy link
Copy Markdown
Member

Thanks @ocean90 pulling this into the 2.0.0 release (current develop). Rebased your two commits onto develop on feature/tenup-content-connect-update-relationships-order #123 , with your authorship preserved (Author: + Co-authored-by: trailer).

Small adjustments while landing it:

  • Resolved a trivial whitespace conflict against develop (kept develop's alignment).
  • Bumped the docblock @since from 1.7.0 → 2.0.0, since 1.7.0 never shipped.
  • Made the @param $object_id doc type-agnostic — the action also fires in the user-to-post case with a user ID, not a post ID.

No behavioral changes to your implementation. Will ship as part of 2.0.0. 🙌

@s3rgiosan s3rgiosan closed this Aug 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Introduce actions after sort order has been updated

2 participants