-
Notifications
You must be signed in to change notification settings - Fork 70
Table caption support #1057
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
base: main
Are you sure you want to change the base?
Table caption support #1057
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -348,6 +348,10 @@ | |||||||||||
| border-top-right-radius: $table-border-radius; | ||||||||||||
| } | ||||||||||||
|
|
||||||||||||
| &-caption { | ||||||||||||
| visibility: hidden; | ||||||||||||
| } | ||||||||||||
|
Comment on lines
+351
to
+353
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 1 Remove the Committable suggestion
Suggested change
Footnotes
|
||||||||||||
|
|
||||||||||||
| &-footer { | ||||||||||||
| background: var(--table-footer-background-color); | ||||||||||||
| color: var(--table-footer-foreground-color); | ||||||||||||
|
|
||||||||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1 Use an enum for the caption positioning options instead of a union type. Caption positioning represents component variants and should follow the established pattern.
Then update the interface:
Also update the default parameter in OcTable.tsx to use
TableCaptionSide.Top.Footnotes
This suggestion is based on your review guideline: "Use interfaces for component props. Prefer enums for component variants, modes, and sizes. Export all types and interfaces. Use descriptive names for types and interfaces. Use proper JSDoc comments to document types. Follow TypeScript best practices for unions, intersections, and optional properties. Use generics to create flexible, reusable types. Avoid circular type dependencies. Use type aliases for complex union or intersection types. Ensure consistent naming conventions across type definitions.
" ↩