Azure Quantum SDK for Azure SDK for JS

[sarangan12]

This is the initial version of Quantum Data Plane SDK.

@ramya-rao-a Please review and approve

@vxfield FYI....

[ramya-rao-a]

@sarangan12, What is the reason that we don't have the same set of npm scripts as other packages? I would imagine that those would part of the scaffolding?

[sarangan12]

These are the scripts that are autogenerated. Do you want to add anything more? Even for attestation, We have started with these initially and added more as needed.

[ramya-rao-a]

Yes, lets add the rest. The catch with keeping them empty is that we then have to remember to fill them up. I'd like to see how many of these we can get filled without issues from the initial commit so that we can set up that as a standard for future new packages

[check-enforcer]

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run js - [service] - ci

[ramya-rao-a]

We don't need minify and prepack scripts in Track 2 right?

[sarangan12]

Removed them.

[ramya-rao-a]

Once the review directory is created in the initial commit, we don't have to recreate it every time the package is built right?

[sarangan12]

The review directory will be created only if it doesn't exist.

[ramya-rao-a]

any reason we cannot fill the above scripts like we have for other packages rather than keeping them as echo skip?

[ramya-rao-a]

I see that you answered in #13345 (comment), I have replied there as well :)

[sarangan12]

The CI actually tries to run them and without actual tests they will fail. Also, we need to ensure each script runs before proceeding forward. Since this is a first commit, I made it to skip

[ramya-rao-a]

Let's do the rest of the npm scripts in a separate PR

[ghost]

Hello @ramya-rao-a!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.