{"id":18480,"date":"2024-02-08T08:00:15","date_gmt":"2024-02-08T16:00:15","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/?p=18480"},"modified":"2024-11-06T12:21:35","modified_gmt":"2024-11-06T20:21:35","slug":"microsoft-graph-toolkit-v4-0-is-now-generally-available","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/microsoft-graph-toolkit-v4-0-is-now-generally-available\/","title":{"rendered":"Microsoft Graph Toolkit v4.0 is now generally available"},"content":{"rendered":"

After a very successful version 3.0<\/a> in June 2023, we are excited to announce the general availability of the Microsoft Graph Toolkit v4.0<\/strong>.<\/p>\n

This release is packed with new capabilities, improvements to the developer experience and bug fixes that will be appreciated by end-users. Starting with v4.0 of Microsoft Graph Toolkit, users will be able to edit To Do items directly using the components, see colleagues\u2019 presence and cards when selecting them via our people picker. We also promoted our search components to their general availability and are now fully supported. For developers, this release greatly improves the developer experience. Our investments were mainly in 2 areas: performance and convenience.<\/p>\n

We introduced<\/a> Microsoft Graph Toolkit in September 2019, and since then, we\u2019ve seen incredible adoption and an amazing response from the developer community and our partners. Our team has been hard at work taking the feedback and requests we\u2019ve received and turning them into the exciting new features we\u2019re excited to share with you today.<\/p>\n

If you are new to the Microsoft Graph Toolkit<\/a>, it is a collection of reusable, framework-agnostic components, and authentication providers for accessing and working with Microsoft Graph. The components are fully functional, customizable, and work with any web framework and on all modern browsers. You can learn more by reading our documentation<\/a> or by trying one of our getting started guides<\/a>.<\/p>\n

What\u2019s new in v4.0?<\/h2>\n

New scenarios: update your To Do items directly within the Toolkit<\/h3>\n

Some feedback we were getting with the Toolkit was that it was providing great productivity enhancements in LOB and ISV apps, but that some of our components were missing key scenarios. To overcome the most requested missing scenario, we added the ability to edit To Do items directly in the component. This enables users to take quick action on their tasks and ensure they are up to date.<\/p>\n

\"A<\/p>\n

More context provided with our people picker<\/h3>\n

Selecting people is critical in productivity scenarios. Whether it is to assign a task to someone or to start a conversation with a group of people, we believe picking people in a rich way is important for end users. To provide more context to this component, we have added the presence of users as part of the control and the ability to see the person\u2019s card of every selected individual.<\/p>\n

<\/p>\n

Build a search-driven application<\/h3>\n

After 6 months of preview, we believe our search components have enough power to provide rich search-driven applications. We have promoted them to GA components to help developers build rich search centers and users to easily find what they are looking for.<\/p>\n

<\/p>\n

Developer experience<\/h2>\n

Improved performance<\/h3>\n

In this version of Microsoft Graph Toolkit, we wanted to focus on performance and drive down the size of the resulting bundles that include our components.<\/p>\n

First, we updated our underlying framework (Lit) to take advantage of asynchronous rendering. This allows our components to be a lot more aware of their state and re-render less often, leaving more memory and cycles for the rest of the page.<\/p>\n

Second, we drastically improved the size of the consumers\u2019 bundles by moving to an explicit registration of the components that are used. With this approach, only the used components are bundled, leaving behind everything that is not necessary. While this has an impact on the developer experience, we believe it will provide a much better user experience.<\/p>\n

Provide more productivity for developers<\/h3>\n

As part of this release, we enhanced numerous aspects of the developer experience to make them more productive and focus on the problems they are trying to solve.<\/p>\n