What about a "preferred" keyword in TypeScript?

Wouldn't it be cool if instead of just public, protected and private, there was also a "preferred" keyword that told IDEs that this is a public method or attribute that was ALSO meant for people to use?

The concept of "public/private" is great for class inheritance. But not so great for building an API. So we resort to naming conventions: An API might have its own internally public methods, but name certain ones certain ways and block calls that try to access them. Wouldn't it be nice if you could say this method is "public" but not "open" to certain calls, or not "preferred" for someone hooking the API? A sprite might have an .x and an ._x, and we assume we should probably assign things to the .x or something weird might happen. But lots of codebases still make ._x public, for various reasons. I'm thinking here of Pixijs's Container.pivot._x. While the underscore is clearly a warning of some kind not to do things this way, there's nothing about public ._x that makes it stand out from public .set(x,y), besides that underscore. Wouldn't it be nice if the suggested methods were somehow, like, suggested by the IDE when you try to use another method to set something like that?

This could be as simple as adding a `preferred` keyword to a public method, and then sticking `prefer [method]` into the comments of another public method that refers to it. Your little light bulb in VSCode would say "You should prefer pivot.set() to directly assigning pivot._x". Or something like that.

Stray thought. Obviously, this is just a sugar concept, doesn't affect code relationships at all, but I feel like it would really help as a way to document code as you go along, especially when some methods do need to be exposed to internal code but really shouldn't be used externally.