Change autoentities patterns.name default value

[RubenCerna2079]

Why make this change?

• Fixes issue [Bug]: autoentities does not honor schema #3455

What is this change?

This changes the default value of the patterns.name property inside autoentities so that it uses both the {schema} and {object} in order to allow users to use multiple objects that have the same name but are from different schemas without the need to do additional changes to the config file.

How was this tested?

• Integration Tests
• Unit Tests
• Manual Tests
  Used sample below to ensure that different entities with the same object name but different schema name can be created without the need to change the patterns.name property.

Sample Request(s)

"AllMagazineObjects": {
  "patterns": {
    "include": [
      "%.magazines"
    ]
  },
  "permissions": [
    {
      "role": "anonymous",
      "actions": [
        {
          "action": "*"
        }
      ]
    }
  ]
}

[Copilot]

Pull request overview

Updates the autoentities default naming pattern so generated entity names include both schema and object, preventing collisions when multiple schemas contain objects with the same name (fix for #3455).

Changes:

• Changed the default autoentities.patterns.name from {object} to {schema}_{object}.
• Updated CLI option help text and JSON schema to reflect the new default.
• Added an MSSQL integration test to validate generation/access of same-named tables across different schemas.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
src/Service.Tests/Configuration/ConfigurationTests.cs	Adds a new MSSQL integration test covering same object name across schemas.
src/Config/ObjectModel/AutoentityPatterns.cs	Changes the default autoentity naming pattern to include schema + object.
src/Cli/Commands/AutoConfigOptions.cs	Updates patterns.name help text to match the new default.
schemas/dab.draft.schema.json	Updates schema description/default for autoentities.patterns.name.

Comments suppressed due to low confidence (3)

src/Service.Tests/Configuration/ConfigurationTests.cs:5618

• This test passes Include: null, which defaults to "%.%" and will auto-generate entities for all eligible tables in the test database. That makes the test slower and more brittle (future schema additions could introduce unrelated naming conflicts). Prefer narrowing patterns.include to just the two tables under test (e.g., foo.magazines and bar.magazines).

                HttpResponseMessage graphqlResponse = await client.SendAsync(graphqlRequest);

                // Assert
                string expectedResponseFragment = @"{""id"":1156,""name"":""The First Publisher""}";

                // Verify number of entities

src/Service.Tests/Configuration/ConfigurationTests.cs:5614

• The autoentity definition key/name PublisherAutoEntity is misleading in a test that is specifically about generating foo_magazines and bar_magazines. Renaming it to something magazines-focused will make failures and logs easier to interpret.

                };
                HttpResponseMessage graphqlResponse = await client.SendAsync(graphqlRequest);

src/Service.Tests/Configuration/ConfigurationTests.cs:5604

• The XML doc comment refers to the default 'property.name', but the configuration property is patterns.name. Updating this avoids confusion when correlating the test with the CLI/schema docs.

                    publishers {
                        items {
                            id
                            name
                        }

[Aniruddh25]

Does this PR also fix the other issue where at the time discovery of metadata for autoentities, dbo is assumed to be the default schema to look for the underlying table? I had opened a different issue for that.

[Aniruddh25]

Dependent on PR #3468