Skip to content

Adding customHosts change in the upgrade guide #468

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

Merged
merged 2 commits into from
Jun 8, 2021
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions changelogs/v3-upgrade-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -66,6 +66,17 @@
### Added `browser` field in package.json.
- The `browser` field indicates the entry point for client applications using Microsoft Graph JS SDK library.

### Added `customHosts` options
- The `AuthenticationHandler` and `TelemetryHandler` will add or update the request headers only if the request URL is a Graph endpoint or a custom endpoint.
- `customHosts` property in `IOptions`, `IClientOptions` takes in a `Set` of custom hosts.

```typescript
// Consider the custom request url is https://CUSTOM_HOST.com
const customHost = "CUSTOM_HOST";
const customHosts = new Set<string>([customHost]);
const client = Client.initWithMiddleware({ middleware, customHosts });
```

### Added `GraphClientError`
- `GraphClientError` handles client-side errors encountered within the JavaScript Client SDK whereas, `GraphError` class should be used to handle errors in the response from the Graph API.

Expand Down