Releases: coinbase/onchainkit
v0.7.0
Minor Changes
-
26f6fd5: - feat: Updated
FrameMetadataType
to supporttarget
for buttonpost
andpost_redirect
actions. By @HashWarlock @Zizzamia #130 #136Note:
In this release we update theFrameMetadataType
so that it supports the latest Handling Clicks Frames specification.If the button clicked is a
post
orpost_redirect
, apps must:- Construct a Frame Signature Packet.
- POST the packet to
fc:frame:button:$idx:target
if present - POST the packet to
fc:frame:post_url if target
was not present. - POST the packet to or the frame's embed URL if neither target nor action were present.
- Wait at least 5 seconds for a response from the frame server.
v0.6.2
v0.6.1
v0.6.0
Minor Changes
- feat: better treeshaking support by using packemon. By @Zizzamia & @wespickett #105 fc74af1
BREAKING CHANGES
For modern apps that utilize ES2020
or the latest version, breaking changes are not anticipated. However, if you encounter any building issues when using OnchainKit with older apps that rely on ES6
, please open an issue and provide details of the error you're experiencing. We will do our best to provide the necessary support.
v0.5.4
Patch Changes
- bf014fd: - feat: exported
FrameButtonMetadata
,FrameInputMetadata
andFrameImageMetadata
types. By @Zizzamia #111- feat: introduced support for image aspect ratio metadata, ensuring backward compatibility. Image metadata can now be defined either as a string (with a default aspect ratio of
1.91:1
) or as an object with a src URL string and an aspect ratio of either1.91:1
or1:1
. By @taycaldwell #110
- feat: introduced support for image aspect ratio metadata, ensuring backward compatibility. Image metadata can now be defined either as a string (with a default aspect ratio of
v0.5.3
Patch Changes
- feat: all
FrameMetadataType
parameters have been updated to use consistent lowerCamelCase. It's important to note that we are not deprecating the old method, at least for a few weeks, to allow time for migration to the new approach. By @Zizzamia #106 f2cf7b6 - feat: while there is no real issue in using either
property
orname
as the standard for a metadata element, it is fair to respect the Open Graph specification, which originally usesproperty
. By @Zizzamia #106
v0.5.2
Patch Changes
- fix:
<FrameMetadata>
component when used with Helmet. To ensure smooth functionality when used with Helmet as a wrapper component, it is crucial to flatten the Buttons loop. By @Zizzamia #99 cefcfa8 - feat: added
Avatar
component, to our Identity Kit. TheAvatar
component primarily focuses on showcasing ENS avatar for given Ethereum addresses, and defaults to a default SVG avatar when an ENS avatar isn't available. By @alvaroraminelli #69
v0.5.1
Patch Changes
- feat: added option for mint action on a Frame. By @Zizzamia #93
- feat: added option for simple static links when creating a Frame. By @Zizzamia #93
- feat: added
wrapper
prop to<FrameMetadata />
component, that defaults toReact.Fragment
when not passed (original behavior). By @syntag #90 #91 - feat: exported
FrameMetadataResponse
type which can be useful when usinggetFrameMetadata
in a TS project. By @syntag #90
v0.5.0
Minor Changes
-
fix: ensured that the
<FrameMetadata>
component uses thename
property instead of theproperty
property to set the type of metadata. Both options are technically correct, but historically, usingname
is more accurate. By @Zizzamia dc6f33d -
feat: renamed the component from
OnchainName
toName
in our Identity Kit. This is a breaking changes. The purpose of the rename is to simplify and enhance clarity. By @alvaroraminelli #86BREAKING CHANGES
To enhance usability and intuitiveness, the component name has been simplified.
OnchainName
is now renamed toName
.Before
import { OnchainName } from '@coinbase/onchainkit'; ... <OnchainName address="0x1234">
After
import { Name } from '@coinbase/onchainkit'; ... <Name address="0x1234">