René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`MODEL_TYPE` not classified as `TSqlFragment` in `CreateExternalModelStatement`","articleBody":"### Description\n\nWhile using the Microsoft ScriptDom parser, I observed an inconsistency in the classification of properties within the `CreateExternalModelStatement` class.\n\nMost properties are correctly identified as `TSqlFragment` types, including:\n\n- `Location`\n- `ModelName`\n- `ApiFormat`\n- `LocalRuntimePath`\n- `Credential`\n- `Parameters`\n\nHowever, the `MODEL_TYPE` field is **not** classified as a `TSqlFragment`, which breaks consistency and complicates tooling that relies on uniform fragment types for parsing and analysis.\n\n---\n\n### 🔍 Expected Behavior\n\n`MODEL_TYPE` should be exposed as a `TSqlFragment`, just like the other fields in `CreateExternalModelStatement`.\n\n---\n\n### ❌ Actual Behavior\n\n`MODEL_TYPE` is not treated as a `TSqlFragment`, making it harder to traverse or extract metadata consistently across all fields.\n\n- **Version**: [170.128.0](https://www.nuget.org/packages/Microsoft.SqlServer.TransactSql.ScriptDom/170.128.0)\n\n---\n\n### 🧪 Steps to Reproduce\n\n1. Parse a `CREATE EXTERNAL MODEL` statement using ScriptDom.\n2. Inspect the resulting `CreateExternalModelStatement` object.\n3. Observe that `MODEL_TYPE` is not a `TSqlFragment`.\n\n---\n\n### ✅ Suggested Fix\n\nUpdate the parser to classify `MODEL_TYPE` as a `TSqlFragment` for consistency and better support in downstream tooling.\n\n---\n\n### 📎 Additional Context\n\nThis change would improve the usability of ScriptDom for scenarios involving AST traversal, formatting, and metadata extraction.\n","author":{"url":"https://github.com/naveennaik1","@type":"Person","name":"naveennaik1"},"datePublished":"2025-10-22T10:00:04.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/176/SqlScriptDOM/issues/176"}