fix(image): explicitly includes fetch priority to avoid filtering

[dzucconi]

I noticed that fetchpriority was actually appearing in the DOM in Force any longer.

It's unclear to me why this is getting filtered out as this was working fine here in Storybook. Possibly something to do with SSR and differences in attribute filtering there... Possibly due to some dependency version difference. Either way, explicitly allowing it should make this work. Checking with a canary.

cc @artsy/diamond-devs

📦 Published PR as canary version: Canary Versions

✨ Test out this PR locally via:

npm install @artsy/[email protected]
npm install @artsy/[email protected]
# or 
yarn add @artsy/[email protected]
yarn add @artsy/[email protected]

[dzucconi]

Huh, yeah still filtering... interesting.

[JanaeHijaz]

I experienced this issue as well. Whenever I use fetchPriority inside of <Image> or <Box>, it would swallow up the fetchPriority prop, worked fine when using <img> instead, weird that it's still filtering now.

[dzucconi]

Yeah, it's related to styled-components props filtering — the question is why it's happening in Force, specifically.