Static Private Class Elements · Issue #42985 · microsoft/TypeScript (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • GitHub Advanced Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Appearance settings

Description

🔍 Search Terms

static private fields methods accessors

✅ Viability Checklist

My suggestion meets these guidelines:

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
• This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion

Add support for static private class elements (fields/methods/accessors). The proposal for adding these in EcmaScript has reached Stage 3. (proposal-static-class-features)

📃 Motivating Example

class ColorFinder { static #red = "#ff0000"; static #green = "#00ff00"; static #blue = "#0000ff";

static colorName(name) { switch (name) { case "red": return ColorFinder.#red; case "blue": return ColorFinder.#blue; case "green": return ColorFinder.#green; default: throw new RangeError("unknown color"); } } }