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

chore: Update dependencies and add Supplier email and phone fields #117

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

MilanKaur-01
Copy link

This commit updates the dependencies in the package.json file of the msgext-northwind-inventory-ts sample. It adds the following dependencies:

  • @azure-rest/communication-messages@1.0.1
  • @azure/communication-email@1.0.0
  • @azure/communication-sms@1.1.0
  • @azure/core-auth@1.6.0

Additionally, it modifies the model.ts file to include the SupplierEmail and SupplierPhone fields in the ProductEx interface. This allows for storing and retrieving the email and phone information of suppliers.

These changes were made to improve the functionality and data representation of the Northwind Inventory sample.

MilanKaur-01 and others added 2 commits May 19, 2024 12:28
This commit updates the dependencies in the package.json file of the msgext-northwind-inventory-ts sample. It adds the following dependencies:
- @azure-rest/communication-messages@1.0.1
- @azure/communication-email@1.0.0
- @azure/communication-sms@1.1.0
- @azure/core-auth@1.6.0

Additionally, it modifies the model.ts file to include the SupplierEmail and SupplierPhone fields in the ProductEx interface. This allows for storing and retrieving the email and phone information of suppliers.

These changes were made to improve the functionality and data representation of the Northwind Inventory sample.
@garrytrinder
Copy link
Collaborator

Thank you for your PR @MilanKaur-01 👏

@BobGerman @rabwill would you be able to review?

@rabwill
Copy link
Collaborator

rabwill commented May 30, 2024

@garrytrinder and @BobGerman Is it more logical to keep the ACS sample as a separate sample, rather than merging it with the existing NW bot, which might be a simpler starting point for beginners?

@garrytrinder
Copy link
Collaborator

@rabwill I think that's a sensible idea.

@BobGerman
Copy link
Collaborator

BobGerman commented May 31, 2024

+1 - I think it should be a separate sample - this sample has become popular on its own and though I love ACS I don't want to add the dependencies for the basic scenario...

@MilanKaur-01 do you mind making a new sample here? Like - copy the whole project to a new folder such as "msgext-northwind-inventory-with-acs" and make a new PR? Thanks!

@MilanKaur-01
Copy link
Author

MilanKaur-01 commented May 31, 2024 via email

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

4 participants