You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently reworking the documentation for library support and ever since I learned of the workspace.userThirdParty setting a couple months ago, I have disliked the name.
It is an incredibly useful feature hidden behind a bad name
The name "Third Party Directory" that is used in the wiki is also a poor choice I feel as it is more than just a directory, that is misleading, it functions closer to an extension and needs a name more fitting of its function.
Possible Solution
A name I have been considering is "Environment Emulators" which could be shortened to envEmulators for the configuration files. I'm still not sure about this name but I think it fits the purpose way better.
They can then be referred to as "third party environment emulators" for the libraries included in meta/3rd/ and as "user environment emulators" for the ones defined in workspace.envEmulators.
The third-party "directories" currently included in meta/3rd/ can continue to be under that directory, I just think the setting and naming of the feature is in desperate need of a change.
Also, if this is to be renamed, it should probably happen at the same time as #1364 to minimize breaking updates.
The text was updated successfully, but these errors were encountered:
Well I know English is not your first language so it is absolutely no problem. I am glad to help improve the English translations and make things as easy to understand as possible.
The Problem
I am currently reworking the documentation for library support and ever since I learned of the
workspace.userThirdParty
setting a couple months ago, I have disliked the name.It is an incredibly useful feature hidden behind a bad name
The name "Third Party Directory" that is used in the wiki is also a poor choice I feel as it is more than just a directory, that is misleading, it functions closer to an extension and needs a name more fitting of its function.
Possible Solution
A name I have been considering is "Environment Emulators" which could be shortened to
envEmulators
for the configuration files. I'm still not sure about this name but I think it fits the purpose way better.They can then be referred to as "third party environment emulators" for the libraries included in
meta/3rd/
and as "user environment emulators" for the ones defined inworkspace.envEmulators
.The third-party "directories" currently included in
meta/3rd/
can continue to be under that directory, I just think the setting and naming of the feature is in desperate need of a change.Also, if this is to be renamed, it should probably happen at the same time as #1364 to minimize breaking updates.
The text was updated successfully, but these errors were encountered: