Skip to content
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

docs: consistent api reference throughout components #5821

Merged
merged 7 commits into from
Nov 30, 2022

Conversation

geospatialem
Copy link
Member

Related Issue: #4442

Summary

  1. Includes consistency across API references, this PR finalizes the style guide across all components.

  2. Also includes the removal of the optional "?" JSDoc tags for the components listed below.

    • A separate PR will be created for the remaining components.

Components included:

  • date-picker
  • dropdown
  • dropdown-group
  • dropdown-item
  • fab
  • filter
  • flow
  • flow-item
  • icon
  • inline-editable

@geospatialem geospatialem requested a review from a team as a code owner November 28, 2022 23:21
@github-actions github-actions bot added the docs Issues relating to documentation updates only. label Nov 28, 2022
Copy link
Member

@driskull driskull left a comment

Choose a reason for hiding this comment

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

❤️‍🔥

@@ -40,19 +40,19 @@ export class DatePickerDay implements InteractiveComponent {
/** Day of the month to be shown. */
@Prop() day!: number;

Copy link
Member

Choose a reason for hiding this comment

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

I wonder if we should undocument these internal date picker components altogether since they aren't designed to be used by an end user.

Copy link
Member Author

Choose a reason for hiding this comment

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

We can remove, as long as the documentation makes sense to the devs and is understandable without the comments when interacting with the components.

Tried to only match the common or same named props for consistency for the devs in those cases, and we could definitely omit altogether if that's the recommend approach. WDYT @driskull?

Copy link
Member

Choose a reason for hiding this comment

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

Lets revisit it later before 1.0.

This component isn't designed for a user to ever read its doc or place it in the DOM.

src/components/inline-editable/inline-editable.tsx Outdated Show resolved Hide resolved
src/components/inline-editable/inline-editable.tsx Outdated Show resolved Hide resolved
@geospatialem geospatialem merged commit db43d9c into master Nov 30, 2022
@geospatialem geospatialem deleted the geospatialem/4442-finalize-component-api-refs branch November 30, 2022 15:57
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants