Question

188

Why can I access TypeScript private members when I shouldn't be able to?

rated 0 times [ 189] [ 1] / answers: 1 / hits: 114188 / 12 Years ago, wed, october 3, 2012, 12:00:00

I'm looking at implementation of private members in TypeScript, and I find it a little confusing. Intellisense doesn't allow to access private member, but in pure JavaScript, it's all there. This makes me think that TS doesn't implement private members correctly.
Any thoughts?

class Test{

  private member: any = private member;

}

alert(new Test().member);

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

ariel

Add To Favorites

Follow

Total Points: 523

Total Questions: 111

Total Answers: 100

Location: Anguilla

Member since Sun, Jan 29, 2023

1 Year ago

ariel questions

1 Typescript with Webpack - You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file

Tue, May 24, 22, 00:00, 2 Years ago

1 why I can't delete .next folder in nextjs project

Thu, Mar 31, 22, 00:00, 2 Years ago

1 How to use NestJS Reflector inside a Custom Decorator?

Tue, Jan 5, 21, 00:00, 3 Years ago

1 How to format date in ant table?

Fri, May 1, 20, 00:00, 4 Years ago

1 ASP.NET Core 3.1 cannot process Axios request until ApiController attribute is added

Mon, Jan 20, 20, 00:00, 4 Years ago

View All

answered 12 Years ago tatianah · Accepted Answer

Just as with the type checking, the privacy of members are only enforced within the compiler.

A private property is implemented as a regular property, and code outside the class is not allowed to access it.

To make something truly private inside the class, it can't be a member of the class, it would be a local variable created inside a function scope inside the code that creates the object. That would mean that you can't access it like a member of the class, i.e. using the this keyword.