Conversation
|
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: 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 |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
triggered prepare-pipelines to try and generate the pipeline for your new ci.yml |
|
/azp run js - resources - ci |
|
Azure Pipelines successfully started running 1 pipeline(s). |
| "dtsRollup": { | ||
| "enabled": true, | ||
| "untrimmedFilePath": "", | ||
| "publicTrimmedFilePath": "./esm/index.d.ts" |
There was a problem hiding this comment.
@sarangan12 also please implement this change as well to follow what Track 2 data-plane packages do.
| "publicTrimmedFilePath": "./esm/index.d.ts" | |
| "publicTrimmedFilePath": "./types/arm-resources.d.ts" |
There was a problem hiding this comment.
@deyaaeldeen Could you please explain what is the impact of not changing it for this release? (We can change it for the next one). Will there be any adverse customer impact or breaking change?
There was a problem hiding this comment.
No correctness issues here, my suggestion is purely to be consistent with data-plane packages.
| "types": "./esm/resourceManagementClient.d.ts", | ||
| "main": "./dist/index.js", | ||
| "module": "./esm/index.js", | ||
| "types": "./esm/index.d.ts", |
There was a problem hiding this comment.
| "types": "./esm/index.d.ts", | |
| "types": "./types/arm-resources.d.ts", |
There was a problem hiding this comment.
No correctness issues here, my suggestion is purely to be consistent with data-plane packages.
| "uglify-js": "^3.4.9" | ||
| }, | ||
| "homepage": "https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/resources/arm-resources", | ||
| "homepage": "https://github.com/Azure/azure-sdk-for-js", |
There was a problem hiding this comment.
@deyaaeldeen This is a minor manual change, which is probably required only for the first time. I would not recommend doing any code level changes for this.
sdk/resources/arm-resources/src/resourceManagementClientContext.ts
Outdated
Show resolved
Hide resolved
sdk/resources/arm-resources/src/resourceManagementClientContext.ts
Outdated
Show resolved
Hide resolved
Co-authored-by: Deyaaeldeen Almahallawi <dealmaha@microsoft.com>
|
I have gone through the comments. Among the comments, there are 3 things:
Now, for the rest of the comments, they seem to be valid. But, at this point, it needs further investigation (things such as publicTrimmedPath, outDir, etc). So, my suggestion is, if you feel that those items must be modified, Please do it manually for this PR and create one consolidated issue with autorest.typescript repository with detailed list of changes required. I can pick it up for the 07/20 release. Please let me know if it sounds good. |
|
@sarangan12 for the rest comments, I don't want to change them manually and include them in the first release. And Aftert codegen is released in 07/20, we can do the second release and include the rest comments. |
|
@dw511214992 We have already created the issue for samples URL. The homepage url might be tricky. But, I can try doing that programmatically. So, include that also when you are creating the issue for the rest of the comments. |
|
@sarangan12 and I talked offline and agreed on prioritizing fixing the samples URL issue since it is a correctness issue. I am fine fixing all other issues after this release, they're just about being consistent with data-plane packages. Keep up the great work guys, I am very excited for this upcoming release! |
|
@sarangan12 I have written a script to change homepage, so if it's not easy to fix it now in codegen side, you can postpone it to next release. thanks |
# Conflicts: # common/config/rush/pnpm-lock.yaml # rush.json
| * Changes may cause incorrect behavior and will be lost if the code is regenerated. | ||
| */ | ||
|
|
||
| // Copyright (c) Microsoft Corporation. |
There was a problem hiding this comment.
This is weird to have both copyright banners, @sarangan12 should we remove the banner from the lro files?
| "esModuleInterop": true, | ||
| "allowSyntheticDefaultImports": true, | ||
| "forceConsistentCasingInFileNames": true, | ||
| "preserveConstEnums": true, |
There was a problem hiding this comment.
why is this needed if we do not generate const enums?
deyaaeldeen
left a comment
There was a problem hiding this comment.
This iteration looks great! I guess all other PRs will look very similar to this one. @sarangan12 could you please look at them?
# Conflicts: # common/config/rush/pnpm-lock.yaml
| * Changes may cause incorrect behavior and will be lost if the code is regenerated. | ||
| */ | ||
|
|
||
| // Copyright (c) Microsoft Corporation. |
There was a problem hiding this comment.
Not a blocking but it seems there are 2 MIT license in this file.
There was a problem hiding this comment.
yes. @deyaaeldeen has commented about it in #16170 (comment)
* @azure/arm-resources track2 * Update sdk/resources/arm-resources/CHANGELOG.md Co-authored-by: Deyaaeldeen Almahallawi <dealmaha@microsoft.com> * update changelog, version in context and add license * remove npm install in prepack * update * udpate pr * update * update * update * update changelog * update changelog Co-authored-by: Deyaaeldeen Almahallawi <dealmaha@microsoft.com> Co-authored-by: qiaozha <qiaozha@microsoft.com>
No description provided.