Skip to content

fix: add renderOrder to AxisRotator#2504

Merged
FarazzShaikh merged 2 commits into
pmndrs:masterfrom
romankoho:fix/2503-renderOrder-AxisRotator
Aug 17, 2025
Merged

fix: add renderOrder to AxisRotator#2504
FarazzShaikh merged 2 commits into
pmndrs:masterfrom
romankoho:fix/2503-renderOrder-AxisRotator

Conversation

@romankoho

@romankoho romankoho commented Aug 1, 2025

Copy link
Copy Markdown
Contributor

Why

this PR closes ticket #2503

What

Checklist

  • Documentation updated (example)
  • Storybook entry added (example)
  • Ready to be merged

I need this urgently ;) would be nice if it can be merged soon

@vercel

vercel Bot commented Aug 1, 2025

Copy link
Copy Markdown

Someone is attempting to deploy a commit to the Poimandres Team on Vercel.

A member of the Team first needs to authorize it.

@codesandbox-ci

codesandbox-ci Bot commented Aug 1, 2025

Copy link
Copy Markdown

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

@romankoho romankoho changed the title add renderOrder to AxisRotator fix: add renderOrder to AxisRotator Aug 1, 2025
@FarazzShaikh

Copy link
Copy Markdown
Member

I’d suggest making it a prop rather than hard coding the renderOrder. Also to preserve backwards compatibility, making the prop optional would be good

@romankoho

Copy link
Copy Markdown
Contributor Author

@FarazzShaikh I agree on that. But in this case I also replaced the hard coded value from ScalingSphere and AxisArrow with the property.

rotationLimits,
scaleLimits,
depthTest = true,
renderOrder = 500,

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Let’s default it to undefined please. As that was the original behavior (backwards compatibility). Unless 500 is absolutely necessary for it to work?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

you are right in regards to the AxisRotator. But if you look at the current code of AxisArrow and ScalingSphere you can see that there the value is hard coded to 500.

So either backwards-compatibility for AxisArrow andScalingSphere is broken or for AxisRotator. I plead for setting the default to 500 as this rather fixes AxisRotator than breaking it. Setting default to undefined could potentially break AxisArrows and ScalingSpheres which were working until now.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@FarazzShaikh if this is a show stopper I'm fine with setting it to undefined.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@FarazzShaikh any opinion on my reply? I'd love to see this being merged.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I’ll merge it tonight. Just need to verify it works as expected with the 500 render order

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

amazing, thank you!

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

hey @FarazzShaikh any update on this? Was there a problem with the render order set to 500?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

merged. Thanks!

@FarazzShaikh FarazzShaikh merged commit 4e48be0 into pmndrs:master Aug 17, 2025
3 of 4 checks passed
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 10.7.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

@romankoho romankoho deleted the fix/2503-renderOrder-AxisRotator branch September 3, 2025 08:34
creativoma pushed a commit to creativoma/drei that referenced this pull request Jan 18, 2026
* add renderOrder to AxisRotator

* add renderOrder property to PivotControls (defaults to 500)

---------

Co-authored-by: Roman <roman.kofler-popp@amrax.ai>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants