microsoft / microsoft/PowerPlatformConnectors
Paths/Accounts issue - flattening file due to limitations of power platform
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.3k
- Forks
- 1.5k
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 11
Description
// missing property "name" ln 27, col 9 (what shows as $ref below)
code is as follows....
"paths": {
"/Accounts": {
"parameters": [
{
"$ref": "#/parameters/requiredHeader",
"type": "string"
}
],
I think the problem is either the "type" shown on line 10 above, or..... if you command-click to the definition....
"parameters": {
"requiredHeader": {
"in": "header",
"name": "xero-tenant-id",
"x-snake": "xero_tenant_id",
"description": "Xero identifier for Tenant",
"example": "YOUR_XERO_TENANT_ID",
"schema": {
"type": "string"
},
"required": true
},
it's either the schema type here, or maybe that parameters is not at level 0 (I don't think it's that however)
Now, changed it to:-
"paths": {
"/Accounts": {
"parameters": [
{
"$ref": "#/parameters/requiredHeader"
}
],
and the error seems to have gone :)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the /Accounts path and the #/parameters/requiredHeader definition shown in the issue. Reproduce the Power Platform validation error with the two parameter forms, then confirm which definition is accepted and identify the corresponding connector source or documentation that should be updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100