Add eng/scripts/DirStructureStats.ps1

[konrad-jamrozik]

No description provided.

[openapi-pipeline-app]

Next Steps to Merge

✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.

[openapi-pipeline-app]

Swagger Validation Report

️️✔️BreakingChange succeeded [Detail] [Expand]

There are no breaking changes.

️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]

There are no breaking changes.

️️✔️CredScan succeeded [Detail] [Expand]

There is no credential detected.

️️✔️LintDiff succeeded [Detail] [Expand]

Validation passes for LintDiff.

️️✔️Avocado succeeded [Detail] [Expand]

Validation passes for Avocado.

️️✔️SwaggerAPIView succeeded [Detail] [Expand]

️️✔️TypeSpecAPIView succeeded [Detail] [Expand]

️️✔️ModelValidation succeeded [Detail] [Expand]

Validation passes for ModelValidation.

️️✔️SemanticValidation succeeded [Detail] [Expand]

Validation passes for SemanticValidation.

️️✔️PoliCheck succeeded [Detail] [Expand]

Validation passed for PoliCheck.

️️✔️SpellCheck succeeded [Detail] [Expand]

Validation passes for SpellCheck.

️️✔️Lint(RPaaS) succeeded [Detail] [Expand]

Validation passes for Lint(RPaaS).

️️✔️PR Summary succeeded [Detail] [Expand]

Validation passes for Summary.

️⌛Automated merging requirements met pending [Detail]

_{Posted by Swagger Pipeline | How to fix these errors?}

[openapi-pipeline-app]

Swagger Generation Artifacts

️️✔️ApiDocPreview succeeded [Detail] [Expand]

_{Posted by Swagger Pipeline | How to fix these errors?}

[openapi-pipeline-app]

PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.

[mikeharder]

Should we do this in pwsh or node? I'd lean towards node.

[weshaggard]

What is the context for these?
I also have https://github.com/Azure/azure-sdk/blob/main/eng/scripts/Update-Spec-Versions.ps1 which builds an index of the specs. I'd like use to have one source of truth if possible for how we determine different aspects. If needed we could move my script to the specs repo.

[konrad-jamrozik]

@mikeharder @weshaggard my intent with these scripts was to share a "starting point" scripts people can use for manual analysis. Like: you dot-source the functions I shared, run them, get the table of results, and do manual post-processing by hand with search-and-replace in notepad++ or whatever (that's how I do it). This is also the reason for using PowerShell, not Node - this is supposed to be easily runnable by hand. Of course I can keep these scripts to myself only, but I figured I might as well share them with the team.

Given this context, do have a better idea how to share them?

[weshaggard]

I don't have any problems including them here but I'm mostly just wanting us to try and get to a point where we can easily have shared code that understands the discovery mechanism of specs.

[konrad-jamrozik]

I'll do the scripts consolidation as part of:

• Develop semantic model of specs repo dir structure azure-sdk-tools#8203

[mikeharder]

Given this context, do have a better idea how to share them?

I think it's premature to add them to the repo, until we have a better idea who else will be using them, and how often. For now, I would share them via another artifact in GitHub, like a closed issue in this repo, or a Public Gist. This is my opinion, but if others disagree, I won't block.

I no longer object

[konrad-jamrozik]

I'll convert this to Gist. Thanks!