[compiler] Move capitalize to compiler

[maorleger]

Follow-up from #7153 (comment) - we noticed that many packages have their own copy of this helper so this PR moves it to the compiler where packages can use it.

[github-actions]

All changed packages have been documented.

• ✅ @typespec/compiler
• ✅ @typespec/openapi3
• ✅ @typespec/protobuf

Show changes

@typespec/compiler - feature ✏️

Add "capitalize" string helper to compiler

@typespec/openapi3 - feature ✏️

Add "capitalize" string helper to compiler

@typespec/protobuf - feature ✏️

Add "capitalize" string helper to compiler

[azure-sdk]

You can try these changes here

🛝 Playground	🌐 Website	🛝 VSCode Extension

[bterlson]

I wonder, should we consider a separate export path for name utils? Could also include case conversions, which is also VERY commonly needed.

[timotheeguerin]

talked with @bterlson and while exporting more right now (like rexporting change-case library) would be too risky of a change, we can plan for th future and include this funciton in /casing subexport instead

import {captialize} from "@typespec/compiler/casing";

[maorleger]

talked with @bterlson and while exporting more right now (like rexporting change-case library) would be too risky of a change, we can plan for th future and include this funciton in /casing subexport instead

import {captialize} from "@typespec/compiler/casing";

Makes sense, and just to be clear this means we want to add a new entry to package.json for this subpath export correct? Happy to do so, just wanted to make sure I understand 👍

[timotheeguerin]

talked with @bterlson and while exporting more right now (like rexporting change-case library) would be too risky of a change, we can plan for th future and include this funciton in /casing subexport instead

import {captialize} from "@typespec/compiler/casing";

Makes sense, and just to be clear this means we want to add a new entry to package.json for this subpath export correct? Happy to do so, just wanted to make sure I understand 👍

yep