JavaScript/TypeScript SDK monorepo for MagicBell - The real-time notification inbox for web & mobile apps
OTHER License
Bot releases are hidden (Show)
Published by MagicBella about 1 month ago
Published by MagicBella about 1 month ago
Published by MagicBella about 1 month ago
71815e7
]:
Published by MagicBella about 1 month ago
Published by MagicBella about 1 month ago
Published by MagicBella about 1 month ago
Published by MagicBella about 1 month ago
6900feb
]:
Published by MagicBella about 1 month ago
71815e7
]:
Published by MagicBella about 2 months ago
Published by MagicBella about 2 months ago
Published by MagicBella about 2 months ago
Published by MagicBella about 2 months ago
Published by MagicBella about 2 months ago
#361 e5027a8
Thanks @smeijer! - Breaking Change!
We've renamed the categories
property to category
and the topics
property to topic
, to reflect that these properties only support a single value. We haven't been supporting multiple categories or topics for a while now, and believe that renaming this property is the right thing to do. It requires a small change on your end, but the clear naming reduces the number of potential bugs caused by misunderstanding.
If you make use of different stores or filters using the categories
or topics
properties, you'll need to rename them to their singular variants.
import { MagicBellProvider } from '@magicbell/react-headless';
const stores = [
{ id: 'default', defaultQueryParams: {} },
{ id: 'unread', defaultQueryParams: { read: false } },
- { id: 'billing', defaultQueryParams: { categories: ['billing'] } },
+ { id: 'billing', defaultQueryParams: { category: 'billing' } },
- { id: 'support', defaultQueryParams: { topics: ['support'] } },
+ { id: 'support', defaultQueryParams: { topic: 'support' } },
];
export default function Index({ children }) {
return (
<MagicBellProvider
apiKey="__MAGICBELL_API_KEY__"
userEmail="__MAGICBELL_USER_EMAIL__"
userKey="__MAGICBELL_USER_KEY__"
stores={stores}
>
{children}
</MagicBell>
);
}
Published by MagicBella about 2 months ago
#361 e5027a8
Thanks @smeijer! - Breaking Change!
We've renamed the categories
property to category
and the topics
property to topic
, to reflect that these properties only support a single value. We haven't been supporting multiple categories or topics for a while now, and believe that renaming this property is the right thing to do. It requires a small change on your end, but the clear naming reduces the number of potential bugs caused by misunderstanding.
If you make use of different stores or tabs using the categories
or topics
properties, you'll need to rename them to their singular variants.
import MagicBell, { FloatingNotificationInbox } from '@magicbell/magicbell-react';
import React from 'react';
const stores = [
{ id: 'default', defaultQueryParams: {} },
{ id: 'unread', defaultQueryParams: { read: false } },
- { id: 'billing', defaultQueryParams: { categories: ['billing'] } },
+ { id: 'billing', defaultQueryParams: { category: 'billing' } },
- { id: 'support', defaultQueryParams: { topics: ['support'] } },
+ { id: 'support', defaultQueryParams: { topic: 'support' } },
];
const tabs = [
{ storeId: 'default', label: 'Latest' },
{ storeId: 'unread', label: 'Archive' },
{ storeId: 'billing', label: 'Billing' },
{ storeId: 'support', label: 'Issues' },
];
export default function Index() {
return (
<MagicBell
apiKey="__MAGICBELL_API_KEY__"
userEmail="__MAGICBELL_USER_EMAIL__"
userKey="__MAGICBELL_USER_KEY__"
stores={stores}
>
{(props) => <FloatingNotificationInbox height={450} tabs={tabs} {...props} />}
</MagicBell>
);
}
e5027a8
]:
Published by MagicBella about 2 months ago
Published by MagicBella about 2 months ago
#361 e5027a8
Thanks @smeijer! - Breaking Change!
We've renamed the categories
property to category
and the topics
property to topic
, to reflect that these properties only support a single value. We haven't been supporting multiple categories or topics for a while now, and believe that renaming this property is the right thing to do. It requires a small change on your end, but the clear naming reduces the number of potential bugs caused by misunderstanding.
If you use topics
or categories
filters in the UserClient
, you'll need to update those params to their singular variant.
import { UserClient } from 'magicbell/user-client';
const magicbell = new UserClient({
apiKey: 'your-api-key',
userEmail: '[email protected]',
});
const notifications = await magicbell.notifications.list({
- categories: ['billing'],
+ category: 'billing',
- topics: ['invoice-1'],
+ topic: 'invoice-1',
});
#360 95bd18d
Thanks @smeijer! - Auth tokens are now prioritized over api keys.
#349 13e54bc
Thanks @smeijer! - define more notification delivery statuses, added skipped
, dropped
, failed
, and delivered
.
Published by MagicBella about 2 months ago
Published by MagicBella about 2 months ago
#299 df2c87f
Thanks @smeijer! - Breaking Change!
We've renamed the categories
property to category
and the topics
property to topic
, to reflect that these properties only support a single value. We haven't been supporting multiple categories or topics for a while now, and believe that renaming this property is the right thing to do. It requires a small change on your end, but the clear naming reduces the number of potential bugs caused by misunderstanding.
If you make use of the categories
or topics
filters on magicbell user notifications
, you'll need to rename them to their singular variants.
- magicbell user notifications list --topics support
+ magicbell user notifications list --topic support
- magicbell user notifications mark-all-read --topics billing
+ magicbell user notifications mark-all-read --topic billing
- magicbell user notifications mark-all-seen --topics other
+ magicbell user notifications mark-all-seen --topic other
#360 95bd18d
Thanks @smeijer! - Auth tokens are now prioritized over api keys.
#349 13e54bc
Thanks @smeijer! - define more notification delivery statuses, added skipped
, dropped
, failed
, and delivered
.
Published by MagicBella about 2 months ago
e5027a8
]:
Published by MagicBella 2 months ago
604cce2
Thanks @renovate[bot]! - Updated dependencies:
@babel/core
to ^7.25.2
.