Skip to content

Circular Option Picker: Use 'placement' prop for popover positioning #70359

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

Conversation

Infinite-Null
Copy link
Contributor

What?

Part of: #44401

This PR updates the Circular Option Picker storybook to use the placement prop instead of the deprecated position prop for its popover.

Why?

The Popover component, used internally by Dropdown, has deprecated the position prop in favor of placement. This update brings the Circular Option Picker storybook in line with the latest standards and maintains consistency with other updated components.

How?

Updated the popoverProps within the Circular Option Picker storybook to use placement: 'top-end' instead of position: 'top right'.

Testing Instructions

To test this change:

  1. Open Storybook
  2. Navigate to the Circular Option Picker component story
  3. Go to with DropdownLinkAction story
  4. Click on learn more

Screenshots:

image

@Infinite-Null Infinite-Null requested a review from ajitbohra as a code owner June 9, 2025 07:00
Copy link

github-actions bot commented Jun 9, 2025

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: Infinite-Null <[email protected]>
Co-authored-by: Mamaduka <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@t-hamano t-hamano added [Type] Code Quality Issues or PRs that relate to code quality [Package] Components /packages/components labels Jun 9, 2025
Copy link
Member

@Mamaduka Mamaduka left a comment

Choose a reason for hiding this comment

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

Thanks, @Infinite-Null!

@@ -5,7 +5,7 @@ import type { Meta, StoryFn } from '@storybook/react';
/**
* WordPress dependencies
*/
import { useState, createContext, useContext } from '@wordpress/element';
import { createContext, useContext, useState } from '@wordpress/element';
Copy link
Member

Choose a reason for hiding this comment

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

Suggestion (non-blocking): This could be due to an ESLint or Prettier configuration, but I recommend avoiding unrelated changes in the future.

@Mamaduka Mamaduka added the props-bot Adding this label triggers the Props Bot workflow for a PR. label Jun 11, 2025
@github-actions github-actions bot removed the props-bot Adding this label triggers the Props Bot workflow for a PR. label Jun 11, 2025
@Mamaduka Mamaduka merged commit 34814c0 into WordPress:trunk Jun 11, 2025
70 of 71 checks passed
@github-actions github-actions bot added this to the Gutenberg 21.1 milestone Jun 11, 2025
chriszarate pushed a commit to chriszarate/gutenberg that referenced this pull request Jul 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Package] Components /packages/components [Type] Code Quality Issues or PRs that relate to code quality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants