Skip to content

Conversation

@JimDaly
Copy link
Member

@JimDaly JimDaly commented Jun 11, 2025

I spent about an hour trying to see which descriptions could be updated using VSCode Copilot Agent mode with this prompt:

Please scan all .cs files in the current workspace. For each file:

1. Only process public interfaces, enumerations, classes, methods, properties, and fields.
2. Do not touch private, internal, or protected members.
3. If a public member already has a /// XML comment, leave it unchanged.
4. If a public member is missing a /// comment, add a basic XML summary comment.
5. Do not modify formatting or indentation.
This operation must be idempotent and safe to run multiple times.

And a little trial & error.

If these descriptions can be updated, then perhaps this reference documentation will be more valuable:
https://learn.microsoft.com/en-us/dotnet/api/microsoft.powerfx.connectors?view=powerfx-sdk-latest

…2920)

I spent about an hour trying to see which descriptions could be updated
using VSCode Copilot Agent mode with this prompt:

```
Please scan all .cs files in the current workspace. For each file:

1. Only process public interfaces, enumerations, classes, methods, properties, and fields.
2. Do not touch private, internal, or protected members.
3. If a public member already has a /// XML comment, leave it unchanged.
4. If a public member is missing a /// comment, add a basic XML summary comment.
5. Do not modify formatting or indentation.
This operation must be idempotent and safe to run multiple times.
```

And a little trial & error.

If these descriptions can be updated, then perhaps this reference
documentation will be more valuable:
https://learn.microsoft.com/en-us/dotnet/api/microsoft.powerfx.connectors?view=powerfx-sdk-latest
@JimDaly JimDaly requested a review from a team as a code owner June 11, 2025 20:26
@jas-valgotar
Copy link
Contributor

✅ No public API change.

@JimDaly
Copy link
Member Author

JimDaly commented Jun 11, 2025

@jas-valgotar can you approve this PR?
@MikeStall approved this earlier version: #2919
But I the test were failing. I thought this was because I was working on a fork of the repo. But now I expect it was actually due to the very strict style requirements, that I finally overcame.

@JimDaly JimDaly enabled auto-merge (squash) June 21, 2025 17:19
@JimDaly
Copy link
Member Author

JimDaly commented Jun 21, 2025

@MikeStall Will you approve this?

@jas-valgotar
Copy link
Contributor

✅ No public API change.

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