Skip to content

fix(react): handle fetchpriority vs fetchPriority #644

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Apr 28, 2024
Merged

fix(react): handle fetchpriority vs fetchPriority #644

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 9 additions & 3 deletions packages/react/src/camelize.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,9 +1,15 @@
import type { HTMLAttributes } from "react";
import * as React from "react";

const nestedKeys = new Set(["style"]);

export const isNewReact = "use" in React;

const fixedMap: Record<string, string> = {
srcset: "srcSet",
fetchpriority: "fetchPriority"
fetchpriority: isNewReact ? "fetchPriority" : "fetchpriority",
};

const camelize = (key: string) => {
if (key.startsWith("data-") || key.startsWith("aria-")) {
return key;
Expand All @@ -14,12 +20,12 @@ const camelize = (key: string) => {
};

export function camelizeProps<TObject extends HTMLAttributes<HTMLElement>>(
props: TObject
props: TObject,
): TObject {
return Object.fromEntries(
Object.entries(props).map(([k, v]) => [
camelize(k),
nestedKeys.has(k) && v && typeof v !== "string" ? camelizeProps(v) : v,
])
]),
) as TObject;
}