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

Add Xiaomi Installation #259

Open
wants to merge 2 commits into
base: Xiaomi
Choose a base branch
from
Open

Add Xiaomi Installation #259

wants to merge 2 commits into from

Conversation

weihengSu2
Copy link

Things to consider before you submit the PR:

  • Are tests passing locally?
  • Are the files formatted correctly?
  • Did you add unit tests?
  • Did you test your change with either the sample apps that are included in the repository or with a blank app that uses your change?

Description

Add Xiaomi Installation classes

@weihengSu2 weihengSu2 changed the base branch from main to Xiaomi March 8, 2023 17:55
@marstr
Copy link
Member

marstr commented Mar 8, 2023

Have these changes been tested with the following method to see if a valid request is generated? Bonus points if it's actually worked against our backend.

public void CreateOrUpdateInstallation(Installation installation)

@weihengSu2
Copy link
Author

weihengSu2 commented Mar 8, 2023

Have these changes been tested with the following method to see if a valid request is generated? Bonus points if it's actually worked against our backend.

public void CreateOrUpdateInstallation(Installation installation)

Yes I will do the actual integration tests today including this one. And thanks very much for the review too! 🙂

mpodwysocki added a commit to Azure/azure-sdk-for-js that referenced this pull request Mar 9, 2023
### Packages impacted by this PR

- @azure/notification-hubs

### Issues associated with this PR


### Describe the problem that is addressed by this PR

Adds Xiaomi support for Track 2 SDKs with registration, installation,
send and send outcome operations.

### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?


### Are there test cases added in this PR? _(If not, why?)_

yes

### Provide a list of related PRs _(if any)_

- Azure/azure-notificationhubs-dotnet#261
- Azure/azure-notificationhubs-dotnet#260
- Azure/azure-notificationhubs-dotnet#259

### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_

### Checklists
- [x] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [x] Added a changelog (if necessary)

---------

Co-authored-by: Jeremy Meng <jeremy.ymeng@gmail.com>
@jessHuh jessHuh self-requested a review March 9, 2023 23:14
Copy link
Member

@jessHuh jessHuh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good to me

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.

None yet

3 participants