Skip to content
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

next release #351

Merged
merged 1 commit into from
Sep 2, 2024
Merged

next release #351

merged 1 commit into from
Sep 2, 2024

Conversation

MagicBella
Copy link
Contributor

@MagicBella MagicBella commented Aug 21, 2024

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@magicbell/[email protected]

Major Changes

  • #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

Minor Changes

  • #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.

Patch Changes

[email protected]

Major Changes

  • #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',
    });

Minor Changes

  • #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.

Patch Changes

  • #348 39832a3 Thanks @smeijer! - removed function to delete push subscriptions, as it doesn't exist on our v1 (current) api.

@magicbell/[email protected]

Major Changes

  • #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>
      );
    }

Patch Changes

@magicbell/[email protected]

Major Changes

  • #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>
      );
    }

Patch Changes

@magicbell/[email protected]

Minor Changes

  • #363 036278a Thanks @smeijer! - use fetch as http client

  • #358 726be74 Thanks @smeijer! - An early release of @magicbell/project-client, a project/admin facing client, to be used on the server, focussing on the MagicBell v2 API.

Patch Changes

@magicbell/[email protected]

Minor Changes

Patch Changes

@magicbell/[email protected]

Patch Changes

@magicbell/[email protected]

Patch Changes

[email protected]

Minor Changes

Copy link

vercel bot commented Aug 21, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
playground ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 2, 2024 7:36am

Copy link

pkg-pr-new bot commented Aug 21, 2024

@magicbell/cli

yarn add https://pkg.pr.new/@magicbell/[email protected]

@magicbell/core

yarn add https://pkg.pr.new/@magicbell/[email protected]

@magicbell/embeddable

yarn add https://pkg.pr.new/@magicbell/[email protected]

@magicbell/in-app

yarn add https://pkg.pr.new/@magicbell/[email protected]

magicbell

yarn add https://pkg.pr.new/[email protected]

@magicbell/project-client

yarn add https://pkg.pr.new/@magicbell/[email protected]

@magicbell/magicbell-react

yarn add https://pkg.pr.new/@magicbell/[email protected]

@magicbell/react-headless

yarn add https://pkg.pr.new/@magicbell/[email protected]

@magicbell/user-client

yarn add https://pkg.pr.new/@magicbell/[email protected]

@magicbell/webpush

yarn add https://pkg.pr.new/@magicbell/[email protected]

commit: 16a7473

@MagicBella MagicBella force-pushed the changeset-release/main branch from f7fb1e4 to 16b70b1 Compare August 21, 2024 12:17
@MagicBella MagicBella force-pushed the changeset-release/main branch from 16b70b1 to 533b487 Compare August 21, 2024 13:17
@MagicBella MagicBella force-pushed the changeset-release/main branch from 533b487 to ac4aa0f Compare August 23, 2024 08:25
@MagicBella MagicBella force-pushed the changeset-release/main branch from ac4aa0f to 9b435f7 Compare August 23, 2024 10:08
@MagicBella MagicBella force-pushed the changeset-release/main branch from 9b435f7 to d138e2a Compare August 23, 2024 12:57
@MagicBella MagicBella force-pushed the changeset-release/main branch from d138e2a to 30ea97f Compare August 23, 2024 14:36
@MagicBella MagicBella force-pushed the changeset-release/main branch from 30ea97f to 4e03dc9 Compare August 23, 2024 14:46
@MagicBella MagicBella force-pushed the changeset-release/main branch from 4e03dc9 to 13354d6 Compare August 26, 2024 03:50
@MagicBella MagicBella force-pushed the changeset-release/main branch from 13354d6 to 347ef9a Compare August 26, 2024 04:03
@MagicBella MagicBella force-pushed the changeset-release/main branch from 347ef9a to 66229fe Compare August 26, 2024 07:34
@MagicBella MagicBella force-pushed the changeset-release/main branch from 66229fe to 50caa5a Compare August 28, 2024 04:41
@MagicBella MagicBella force-pushed the changeset-release/main branch from 50caa5a to 6e32618 Compare August 29, 2024 05:20
@MagicBella MagicBella force-pushed the changeset-release/main branch from 6e32618 to 6fa61ef Compare August 30, 2024 03:43
@MagicBella MagicBella force-pushed the changeset-release/main branch from 6fa61ef to 4efbe5a Compare August 30, 2024 09:15
@MagicBella MagicBella force-pushed the changeset-release/main branch from 4efbe5a to d80335e Compare August 30, 2024 10:02
@MagicBella MagicBella force-pushed the changeset-release/main branch from d80335e to 2552a21 Compare August 30, 2024 10:34
@MagicBella MagicBella force-pushed the changeset-release/main branch from 2552a21 to 17506e2 Compare August 30, 2024 19:20
@MagicBella MagicBella force-pushed the changeset-release/main branch from 17506e2 to 126b345 Compare August 30, 2024 19:44
@MagicBella MagicBella force-pushed the changeset-release/main branch from 126b345 to a7a948f Compare September 1, 2024 04:35
@MagicBella MagicBella force-pushed the changeset-release/main branch from a7a948f to abaf0b6 Compare September 2, 2024 07:28
@MagicBella MagicBella force-pushed the changeset-release/main branch from abaf0b6 to ffa471f Compare September 2, 2024 07:30
@MagicBella MagicBella force-pushed the changeset-release/main branch from ffa471f to 16a7473 Compare September 2, 2024 07:32
@smeijer smeijer merged commit 8dda154 into main Sep 2, 2024
8 checks passed
@smeijer smeijer deleted the changeset-release/main branch September 2, 2024 08:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants