I guess it is fair for the cases when the tool spawns jobs and does some work as daemons - like services, monitoring, alerting, etc. In this case data stays with XYZ database.
But I agree that we need a public registry of "safe" Class/Global prefixes and names.
We can take some easy and obvious approaches: Github or DNS.
E.g. with the Gihub approach the package name can start with a company.reponame.
Like the clickable InterSystems Data Platforms tags in the repo:
@Dmitry Maslennikov , could you share, please, the code to be inserted into Reaadme.md to introduce it into the repo?
Yes, you cannot change the content of an accepted answer.
we did this intentionally: what is the reason to change the answer, which resolved the question?
New cool update came up with VSCode!
What's new in this version
"objectscript.conn.active": trueto enable itobjectscript.autoPreviewXML)..Name,..SomeMethod()Well done, Dmitry!
This limit on Comunity Edition will be expanded with the next update.
Thank you, Vitaly! ObjectScript is full of opportunities! With a creative community, of course :)
But why "minus"? This is elegant and works.
You cannot, yes because of Accepted status.
Hi Sergey! Do not take Community Edition limits into consideration.
If you don't have limits what is the best strategy with packages/tools development in your opinion?
Yes, you are right.
I guess it is fair for the cases when the tool spawns jobs and does some work as daemons - like services, monitoring, alerting, etc. In this case data stays with XYZ database.
But I agree that we need a public registry of "safe" Class/Global prefixes and names.
We can take some easy and obvious approaches: Github or DNS.
E.g. with the Gihub approach the package name can start with a company.reponame.
Thoughts?
Thanks, Kyle!