search

microsoftgraph / msgraph-sample-reactspa

This sample demonstrates how to use the Microsoft Graph JavaScript SDK to access data in Office 365 from React browser apps.
MIT License
125 stars 105 forks source link

Bump @microsoft/mgt-element from 3.1.3 to 4.1.0 in /graph-tutorial #242

Closed dependabot[bot] closed 6 months ago

dependabot[bot] commented 7 months ago

Bumps @microsoft/mgt-element from 3.1.3 to 4.1.0.

Release notes

Sourced from @​microsoft/mgt-element's releases.

v4.1.0

4.1.0 (2024-02-26)

Features

  • add ability to disable suggestions on people-picker (#3048) (f174714)
  • move electron to peer dependency (#3046) (c572c01)

Bug Fixes

  • make scope aware requests work for electron apps (c572c01)

v4.0.1

4.0.1 (2024-02-12)

Bug Fixes

  • apply keyboard focus when removing selected person or adding person from suggestion list on people-picker (#3011) (8c8b138)
  • ensure consistency level header present for user search (#3029) (3d893b2)

v4.0.0

4.0.0 (2024-02-05)

⚠ BREAKING CHANGES

  • mgt-loader.js is removed and there is no support for es5 only browsers direct from CDN. Developers loading mgt from a CDN must use module syntax and explicitly initialize their applications.
  • mgt-spfx is deprecated, use disambiguation instead
  • ViewType is now a string union type and not an enum
  • UserType is now a string union type and not an enum
  • PersonType is now a string union type and not an enum
  • GroupType is now a string union type and not an enum
  • groupType property on MgtPeoplePicker is now a GroupType[] not a GroupType that is a bitmask of the desired group types. Developers using the group-type attribute will find the behavior unchanged.
  • the avatarType eunm has been renamed to AvatarType for consistency and converted to a string union type
  • the ResponseType for mgt-get is now a string union type and not an enum
  • PersonCardInteraction is now a string union type and not an enum
  • convert attribute enums to string unions (#2962)
  • PersonViewType has been removed. 'avatar' is no longer a valid value for the 'view' attribute on the 'mgt-person' component
  • permissions: applications using mgt-person with fetch-image and person-detal where the supplied value is a group will now need to consent to either Group.Read.All or Group.ReadWrite.All. This replaces the existing behavior where the group image would silently fail to load and show an http 403 error in the console.
  • permissions: minimal permission for planner calls changed from Group.ReadWrite.All to Tasks.ReadWrite for write operation and from Group.Read.All to Tasks.Read for read operations.
  • prepScopes now accepts an array of scopes, this is checked against the set of currently consented scopes for the user. If any of the supplied scopes are found, then no additional scopes are requested. If no match is found, then the user will be prompted to consent to the first scope in the supplied array of scopes
  • mgt-tasks has been removed and replaced with mgt-planner. mgt-planner does not support data-source switching to fetch data from the outlook tasks apis any longer.
  • Developers must explicitly call the register function for all web components used in their application when using components from @microsoft/mgt-components. Importing from the root of @microsoft/mgt-components no longer has an automatic registration side effect. NOTE Components from @microsoft/mgt-react will automatically register the underlying web component when they are used for the first time.
  • MgtPersonCard no longer has a static config property.This config has been moved to the MgtPersonCardConfig class to allow developers to import the config and associated getMgtPersonCardScopes function at the top level of their applicaiton without automatically adding the weight of the full mgt-person-card component and dependencies to the entry file for their applications.
  • default behavior of mgt-people-picker changes so presence is not shown unless show-presence attribute or showPresence property are set
  • applications importing @microsoft/mgt-react but not using the wrapper components will not have components automatically registered in the browser. This leads to a breaking change when these applications emit raw web component markup rather than using the wrapper components.

... (truncated)

Changelog

Sourced from @​microsoft/mgt-element's changelog.

4.1.0 (2024-02-26)

Features

  • add ability to disable suggestions on people-picker (#3048) (f174714)
  • move electron to peer dependency (#3046) (c572c01)

Bug Fixes

  • make scope aware requests work for electron apps (c572c01)

4.0.1 (2024-02-12)

Bug Fixes

  • apply keyboard focus when removing selected person or adding person from suggestion list on people-picker (#3011) (8c8b138)
  • ensure consistency level header present for user search (#3029) (3d893b2)

4.0.0 (2024-02-05)

⚠ BREAKING CHANGES

  • mgt-loader.js is removed and there is no support for es5 only browsers direct from CDN. Developers loading mgt from a CDN must use module syntax and explicitly initialize their applications.
  • mgt-spfx is deprecated, use disambiguation instead
  • ViewType is now a string union type and not an enum
  • UserType is now a string union type and not an enum
  • PersonType is now a string union type and not an enum
  • GroupType is now a string union type and not an enum
  • groupType property on MgtPeoplePicker is now a GroupType[] not a GroupType that is a bitmask of the desired group types. Developers using the group-type attribute will find the behavior unchanged.
  • the avatarType eunm has been renamed to AvatarType for consistency and converted to a string union type
  • the ResponseType for mgt-get is now a string union type and not an enum
  • PersonCardInteraction is now a string union type and not an enum
  • convert attribute enums to string unions (#2962)
  • PersonViewType has been removed. 'avatar' is no longer a valid value for the 'view' attribute on the 'mgt-person' component
  • permissions: applications using mgt-person with fetch-image and person-detal where the supplied value is a group will now need to consent to either Group.Read.All or Group.ReadWrite.All. This replaces the existing behavior where the group image would silently fail to load and show an http 403 error in the console.
  • permissions: minimal permission for planner calls changed from Group.ReadWrite.All to Tasks.ReadWrite for write operation and from Group.Read.All to Tasks.Read for read operations.
  • prepScopes now accepts an array of scopes, this is checked against the set of currently consented scopes for the user. If any of the supplied scopes are found, then no additional scopes are requested. If no match is found, then the user will be prompted to consent to the first scope in the supplied array of scopes
  • mgt-tasks has been removed and replaced with mgt-planner. mgt-planner does not support data-source switching to fetch data from the outlook tasks apis any longer.
  • Developers must explicitly call the register function for all web components used in their application when using components from @microsoft/mgt-components. Importing from the root of @microsoft/mgt-components no longer has an automatic registration side effect. NOTE Components from @microsoft/mgt-react will automatically register the underlying web component when they are used for the first time.
  • MgtPersonCard no longer has a static config property.This config has been moved to the MgtPersonCardConfig class to allow developers to import the config and associated getMgtPersonCardScopes function at the top level of their applicaiton without automatically adding the weight of the full mgt-person-card component and dependencies to the entry file for their applications.
  • default behavior of mgt-people-picker changes so presence is not shown unless show-presence attribute or showPresence property are set
  • applications importing @microsoft/mgt-react but not using the wrapper components will not have components automatically registered in the browser. This leads to a breaking change when these applications emit raw web component markup rather than using the wrapper components.

Features

... (truncated)

Commits


Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

dependabot[bot] commented 6 months ago

Superseded by #272.