-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Rename meta
types for consistency
#378
Conversation
BREAKING CHANGE: Consumers will need to update their type imports. This renames `MetaDescriptor` to `HtmlMetaDescriptor` for better consistency with `HtmlLinkDescriptor`. `remix-server-runtime` also exposed a type `HTMLLinkDescriptor` with inconsistent casing, so I changed that as well.
[name: string]: string | string[]; | ||
} | ||
|
||
export type MetaDescriptor = HtmlMetaDescriptor; |
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.
This alias is for consistency with LinkDescriptor
, even though HtmlMetaDescriptor
will only ever be HtmlMetaDescriptor
(probably). Gives us a little wiggle room if we ever change that.
Sorry I screwed up your doc updates, want to fix the conflicts and then I'll merge :) |
Thank you for signing the Contributor License Agreement. Let's get this merged! 🥳 |
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.
Thank you for documenting this! 👍 Looks good to me. I'd like someone else to check on this as well because it's a breaking change. jk, looks like you're good to merge once you have conflicts resolved
BREAKING CHANGE: Consumers will need to update their type imports. This renames
MetaDescriptor
toHtmlMetaDescriptor
for better consistency withHtmlLinkDescriptor
.remix-server-runtime
also exposed a typeHTMLLinkDescriptor
with inconsistent casing, so I changed that as well.I've also exported both types from
@remix-run/react
directly which makes predictive imports in VS Code a little better IMO.