Revise DirectConnector branding and README to reflect current SDK architecture

Open
#7 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Quiet
Tech stack
csharp
Domain
developer-experience, documentation

Research direction

Start by locating the DirectConnector project folder, its namespace declarations, the README, and the solution file project reference. Review the existing terminology and SDK architecture described in the repository before choosing a replacement name. Done means the folder, namespace, README, historical references, and solution reference consistently use the new branding.

Written by the indexing model from the issue text.

Description

enhancement

The DirectConnector name is inherited from the early prototype that directly accessed API Hub before the Connectors SDK or AI Gateway existed. This branding is likely to cause confusion now.

Tasks:

  • Rename the project folder and namespace from DirectConnector to something more descriptive (e.g., ConnectorsSample, FunctionsConnectorSample)
  • Update the README content to better reflect the current SDK-based architecture
  • Remove historical artifacts and terminology that reference the old direct-access approach
  • Update the solution file project reference
Dominant language
C#
Stars
3
Forks
3
Avg merge
1h 8m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/Connectors-NET-Samples

All issues in Azure/Connectors-NET-Samples

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.