Skip to content

Conversation

@DitwanP
Copy link
Contributor

@DitwanP DitwanP commented Jan 13, 2026

Related Issue: #12833

Summary

Audit following components for doc style guid consistency:

  • accordion-item
  • accordion
  • action-bar
  • action-group
  • action-menu (Internal)
  • action-pad (Deprecated but wont be removed until v6)
  • action
  • alert
  • autocomplete-item-group
  • autocomplete-item
  • autocomplete
  • avatar

@DitwanP DitwanP requested a review from a team January 13, 2026 22:55
@DitwanP DitwanP added the skip visual snapshots Pull requests that do not need visual regression testing. label Jan 13, 2026
@github-actions github-actions bot added the docs Issues relating to documentation updates only. label Jan 13, 2026
Copy link
Member

@geospatialem geospatialem left a comment

Choose a reason for hiding this comment

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

Awesome, @DitwanP! 🙌🏻 Similar to Mel's PR it looks like there are a number of changes that would apply across components - for consistency we will need to make a call across all components.

If we do decide to adopt new accepted language across components, we could add a new list of updates that could be applied to the related issue for us to follow with the doc consistency effort.

cc @Esri/calcite-pes

//#region Public Properties

/** Specifies the accessible label for the last `calcite-action-group`. */
/** Specifies an accessible name for the last `calcite-action-group`. */
Copy link
Member

Choose a reason for hiding this comment

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

Think this would still be a label rather than name?

@property({ reflect: true }) expanded = false;

/** Accessible name for the component. */
/** Specifies an accessible name for the component. */
Copy link
Member

Choose a reason for hiding this comment

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

Similar to feedback on @DintaMel's PR, we should align on common language to the label property across components.

Comment on lines +102 to +106
* Specifies the type of positioning to use for overlaid content, where:
*
* Using `"absolute"` will work for most cases. The component will be positioned inside of overflowing parent containers and will affect the container's layout.
* `"fixed"` should be used to escape an overflowing parent container, or when the reference element's `position` CSS property is `"fixed"`.
* `"absolute"` positions the component inside of overflowing parent containers and will affect the container's layout, and
*
* `"fixed"` is used to escape an overflowing parent container, or when the reference element's `position` CSS property is `"fixed"`.
Copy link
Member

Choose a reason for hiding this comment

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

Similar to the label property, we should align on language across components.

@property({ reflect: true }) overlayPositioning: OverlayPositioning = "absolute";

/** Arranges the component depending on the element's `dir` property. */
/** Specifies the position of the component depending on the element's `dir` property. */
Copy link
Member

Choose a reason for hiding this comment

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

It looks like the same language is used in action-pad should we keep it as-is or change for both for consistency? Possibly even use "Positions the component..."? cc @Esri/calcite-pes

@property({ reflect: true }) inputValueMatchPattern: RegExp;

/** Accessible name for the component. */
/** Specifies an accessible name for the component. */
Copy link
Member

Choose a reason for hiding this comment

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

Same as other properties for consistency, similar to feedback in Mel's PR for alignment with label.

@property() inputValue: string;

/** Accessible name for the component. */
/** Specifies an accessible name for the component. */
Copy link
Member

Choose a reason for hiding this comment

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

Similar to the label property above for naming consistency across components.

Comment on lines +247 to +251
* Specifies the type of positioning to use for overlaid content, where:
*
* Using `"absolute"` will work for most cases. The component will be positioned inside of overflowing parent containers and will affect the container's layout.
* `"absolute"` positions the component inside of overflowing parent containers and will affect the container's layout, and
*
* `"fixed"` should be used to escape an overflowing parent container, or when the reference element's `position` CSS property is `"fixed"`.
* `"fixed"` is used to escape an overflowing parent container, or when the reference element's `position` CSS property is `"fixed"`.
Copy link
Member

Choose a reason for hiding this comment

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

Similar to the overlayPositioning property above for naming consistency across components.


/**
* Determines where the component will be positioned relative to the container element.
* Specifies where the component is positioned relative to the container element.
Copy link
Member

Choose a reason for hiding this comment

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

There are a few components with similar language, when agreed upon language, we should add this to the list in the original issue for future doc consistency suggestions. 💪🏻


/**
* The current validation state of the component.
* Specifies the current validation state of the component.
Copy link
Member

Choose a reason for hiding this comment

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

There are a few components with similar language, when agreed upon language, we should add this to the list in the original issue for future doc consistency suggestions. 💪🏻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Issues relating to documentation updates only. skip visual snapshots Pull requests that do not need visual regression testing.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants