Evgeny Shvarov · Jan 10, 2025 go to post

Isn't it more safe to have a clear namesepace/database for the code base with every CI/CD phase? 

Evgeny Shvarov · Jan 8, 2025 go to post

What about the data (globals) left related to deleted classes? SHould it be deleted as well?

Evgeny Shvarov · Dec 31, 2024 go to post

Why discuss 100+ rules? 

I don't care honestly which rules ObjectScript Quality's clients would like to enforce in their organisation.

By providing a free-of-charge scanning with this tool (which is not InterSystems one), we use only 11 rules that we think are useful for the developer community. And we are more than happy to expand these 11 to more or improve current.

For 100 + other rules we don't care.

Evgeny Shvarov · Dec 31, 2024 go to post

Why are we discussing too many properties and too many methods rules?

For InterSystems Developer Community we use only 11 rules.

Is "variable not found" a bad rule?

I faced this issue many times, even in my code, and found it very helpful. What is bad that public ObjectScript repositories will be scanned for free for such an error?

Could we discuss these 11 rules that are being used? 

Which else rules could be useful and potentially could be added?

Evgeny Shvarov · Dec 29, 2024 go to post

Hi @Herman Slagman ! What changes do you want to see?

Yes, new ObjectScript rules for SonarQube should be coded in Java.

Still don't understand why the tool is bad? If the rules do not fit your requests why not suggest at least one here? 

Evgeny Shvarov · Dec 27, 2024 go to post

Thanks for the feedback, @Muhammad Waseem!

I encourage developers to share what else they fill make their developer life better in day-to-day routine development so it can be helpful for others too. 

Evgeny Shvarov · Dec 27, 2024 go to post

Yes, I agree!

Let’s discuss and introduce rules that are really helpful. For the record: 16 rules we use now is the selection out of 100+.

Evgeny Shvarov · Dec 16, 2024 go to post

Also it'd be great to search/filter globals in the list, ideally with wildcards, e.g. ^Project*

Evgeny Shvarov · Dec 16, 2024 go to post

Great initiative!

Reading works, but editing and saving doesn't. Created global ^AAA first (in terminal), then read it in VSCode, opened YAML file, edited, saved in /data/gl folder - how can data can be imported to IRIS?

Evgeny Shvarov · Nov 4, 2024 go to post

I think open-source and private IP policy should be balanced. But Microsoft's financial success and approach which let company to become a largest contributor to open-source could be a good argument that balanced open-source contribution maybe connected to company's prosperity.

Evgeny Shvarov · Nov 4, 2024 go to post

Regarding user/pass - it should be a user and his/her password that is allowed to access web app /registry in your IRIS server.

You can go to the list of Web Apps: http://localhost:52773/csp/sys/sec/%25CSP.UI.Portal.Applications.WebLis… and observe other and setup your own.

It can be passwordless, basic authentication, bearer token, OAuth, delegated - whatever you decide in your system.

If you are on a community edition of IRIS from a vanilla iris docker image then login/pass you use for your admin access, e.g. to access Management Portal http://localhost:32783/csp/sys/%25CSP.Portal.Home.zen

will work for the registry as well.

Evgeny Shvarov · Nov 3, 2024 go to post

There are two steps to publish into a registry. 

1. Load a package into a namespace - you can load from a file directory that contains module.xml, or from a github repo, e.g.

load /folder_with_module/

2. switch to a current registry, where you can publish. You can install your own registry, or use  a test registry, which is always avaliable for different tests:

ZPM:USER>repo -n registry -r -url https://test.pm.community.intersystems.com/registry/ -user test -pass PassWord42

3. Publish a pachage with the command:

publish package_name