Skip to content

Conversation

@Data247logic
Copy link
Contributor


Please check the following conditions for your PR.

  • apiDefinition.swagger.json is validated using paconn validate command.
  • apiProperties.json has a valid brand color. Invalid brand colors are #007ee5 and #ffffff.

calvinleong and others added 14 commits November 5, 2020 11:58
)

* Update apiDefinition.swagger.json

* Add files via upload

* update readme

* Update Get User Info Action and apiProperties file
* Create IN-D KYC India

* Delete IN-D KYC India

* Create apiDefinition.swagger.json

* Add files via upload

* Create README.MD

* Update README.MD

* Delete README.MD

* Delete apiDefinition.swagger.json

* Delete apiProperties.json

* Create IN-D Insurance

* Delete IN-D Insurance

* Create IN-D Insurance

* Delete IN-D Insurance

* Create Readme.md

* Add files via upload

* Add files via upload

* Delete Readme.md

* Delete apiDefinition.swagger.json

* Delete apiProperties.json

* Create Readme.md

* Add files via upload

* Add files via upload
@Data247logic Data247logic requested a review from a team as a code owner November 26, 2020 23:10
@ghost
Copy link

ghost commented Nov 26, 2020

CLA assistant check
All CLA requirements met.

Copy link
Contributor

@dougelliott dougelliott left a comment

Choose a reason for hiding this comment

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

In addition to the comments, you can also remove the icon.png and settings.json file from this PR, as they don't need t be open sourced. The icon will be provided during the submission process within ISV Studio.

dougelliott
dougelliott previously approved these changes Dec 22, 2020
@Data247logic
Copy link
Contributor Author

Data247logic commented Dec 23, 2020 via email

dougelliott
dougelliott previously approved these changes Dec 23, 2020
@sriyen-msft
Copy link
Contributor

sriyen-msft commented Dec 24, 2020

Hi Doug, Sorry for the delay, I was busy with other things, I have done all the changes in suggested by you and your colleague. Can you please review and let me know what is next step to proceed further. waiting for your reply... Regards, M.i

On Tue, Dec 22, 2020 at 9:39 AM Doug Elliott @.> wrote: @.* approved this pull request. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#584 (review)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARLGTDU5JTRTD67YGMR3IOTSWALXZANCNFSM4UEHR3ZA .

@Data247logic There seems few comments need to be fixed, Can you please resolve the comments (Click on "resolve conversation") you have already fixed.

@Data247logic
Copy link
Contributor Author

Data247logic commented Jan 3, 2021 via email

@dougelliott
Copy link
Contributor

@Data247logic I've gone ahead and resolved the comments that seem to have been addressed. So all the pending comments left by Srikanth and myself should be addressed in another commit. Please let us know if there are any questions about the feedback.

@Data247logic
Copy link
Contributor Author

Data247logic commented Jan 6, 2021 via email

@Data247logic
Copy link
Contributor Author

Data247logic commented Jan 11, 2021 via email

@dougelliott
Copy link
Contributor

@Data247logic I've already approved the PR, but it is now pending a review from my colleague, @sriyen-msft . He will provide another round of reviews on your changes soon, and will follow up with any further points of feedback.

"/v3.0/MT/": {
"get": {
"responses": {
"default": {
Copy link
Contributor

Choose a reason for hiding this comment

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

Please replace ALL the "default" responses with expected status codes, otherwise users may see errors about incorrect schema instead of real error responses from your service in OpenAPI mode.

@Data247logic
Copy link
Contributor Author

Data247logic commented Jan 19, 2021 via email

@sriyen-msft
Copy link
Contributor

sriyen-msft commented Jan 21, 2021

Hi, I am not getting you, can you please give me one example so that i can fix it and finish this off. waiting for your reply... regards, M.i

On Fri, Jan 15, 2021 at 5:41 AM Srikanth Yenagandhula < @.> wrote: @.* requested changes on this pull request. ------------------------------ In certified-connectors/Data247logic/apiDefinition.swagger.json <#584 (comment)> : > + "contact":{ + "name":"Data247 Support", + "url":"https://support.data247.com/" + } + }, + "host": "api.data247.com", + "basePath": "/", + "schemes": [ + "https" + ], + "paths": { + "/v3.0": {}, + "/v3.0/MT/": { + "get": { + "responses": { + "default": { Please replace ALL the "default" responses with expected status codes, otherwise users may see errors about incorrect schema instead of real error responses from your service in OpenAPI mode. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#584 (review)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARLGTDTE5RZLSUWHZM2M2MDSZ6B2FANCNFSM4UEHR3ZA .

Example - 365 Training

@Data247logic
Copy link
Contributor Author

Data247logic commented Jan 24, 2021 via email

@dougelliott
Copy link
Contributor

@sriyen-msft Please re-review the changes that @Data247logic has made. Thanks!

@sriyen-msft
Copy link
Contributor

@Data247logic Can you please remove extra files added to this PR

image

@Data247logic
Copy link
Contributor Author

Data247logic commented Jan 28, 2021 via email

@Data247logic
Copy link
Contributor Author

Data247logic commented Feb 3, 2021 via email

@sriyen-msft
Copy link
Contributor

@Data247logic I am not sure whether you are familiar or not with Github and PR pipeline, But please make sure that there is no "Swagger and Change Validation" errors in "checks" section of the PR whenever you push any commit. There are 10+ errors flagged, please fix them.

https://github.com/microsoft/PowerPlatformConnectors/pull/584/checks

##[error]The 'summary' value must end with alphanumeric character. ValuePath: /paths/~1v3.0~1MT~1/get/summary
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/~1v3.0~1MT~1/get/responses/default
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/~1v3.0~1CU~1/get/responses/default
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/~1v3.0~1CT~1/get/responses/default
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/~1v3.0~1CI~1/get/responses/default
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/~1v3.0~1VE~1/get/responses/default
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/~1v3.0~1VA~1/get/responses/default
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/~1v3.0~1VP~1/get/responses/default
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/~1v3.0~1AP~1/get/responses/default
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/~1v3.0~1AE~1/get/responses/default
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/~1v3.0~1APR~1/get/responses/default
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/~1v3.0~1AER~1/get/responses/default
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/~1v3.0~1AR~1/get/responses/default
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/~1v3.0~1AN~1/get/responses/default
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/~1v3.0~1AG~1/get/responses/default
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/~1v3.0~1AZ~1/get/responses/default
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/~1v3.0~1AZR~1/get/responses/default
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/~1v3.0~1GI~1/get/responses/default
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/~1v3.0~1DC~1/get/responses/default
##[error]The 'default' response should not have schema definition. Schemas should be defined on expected responses only. ValuePath: /paths/~1v3.0~1TPC~1/get/responses/default

@dougelliott
Copy link
Contributor

@Data247logic Checking in on the feedback that Srikanth provided above. Do you have any questions about that?

@dougelliott dougelliott merged commit eb3bccf into microsoft:dev Feb 24, 2021
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.

5 participants