Hi Paul!
I suggest to take a look two mechanisms:
1. merge cpf - you can list the configuration changes made to vanilla iris/or your custom image.
2. IPM
with IPM you can deploy classes, web apps, files and production elements, run install scripts and version product changes.
I see, makes sense
I see that coding guidlines for ObjectScript linter should be a document (json? yaml?) you include in your code repository or reference any file in a github/gitlab and VSCode linter follows it on-the-go.
Or as some ObjectScript.Quality like ruleset, is it possible @Daniel Tamajon ?
Or as a codetidy feature by @Timothy Leavitt, but it's not easy to use.
This is great, @Ben Spead! Could you please provide an example of how any developer can leverage the code guidelines @Robert Barbiaux suggests in this post?
Voted.
Rebuild indices, this could be the case.
Great points, Dima. But I think any discussions make sense - this is how people communicate and exchange ideas, as you did in your post as well. We could request ObjectScriptQuality to add a profile that will enforce the rule and also, there is a linter in VSCOde ObjectScript - maybe it is possible to request the change in it too.
The idea of an open-source parser for ObjectScript - a good one, do we have it published on the ideas portal?
Are you sure you want to see that many rectangles on a treemap?
Thank you, @Jonathan Lent ! Pleasure to hear we are still better in some spaces than bots :)
Hi @Jonathan Lent !
Great question!
It is supported. You can take a look at the Interoperability template on Open Exchange.
Here is the line of code in a module.xml file.
Great example of custom class queries, @Timothy Leavitt !
I wonder if the recursion with ..AllFetch() is necessary here and in every case?
Very useful article, a lot of use-cases and examples! Thank you @Ashok Kumar Thangavel !
Exciting initiative!
I think this line in Update is "orphaned":
set myobj = ##class(%Library.DynamicObject).%FromJSON(%request.Content) @Justin Millette, there are more settings to enable in the system to allow delegated access, e.g. a system-wide setting, mentioned in this great @Pravin Barton's article , also there is another one from @Yuri Marx
Also, I don't recommend using the WebApplication tag as it is not working properly yet; there is at least one important bug not solved: for example , CSPApplication works quite well.
Also, I see %all - I hope this is for development/demo usage only, as it is quite a generous role to use.
Great stuff!
Made an example in ObjectScript Docker template:
@Thomas Wuppermann, you can add an env variable in docker-compose.yml to make merge cpf be implied, and the merge.cpf with the name you prefer.
On a side note, have you tried ObjectScript Quality for the same linting purpose? It is very naturally connected to GitHub Actions - you can add this file to any open-source GitHub repository with objectscript to see it in action, with examples.
I think it's worth pinging CodeTidy's author @Timothy Leavitt
I agree. I changed it to "not read-only" as I wasn't to manage unit-tests without it :)
Don't know how to mark an object "modified" - otherwise, %Save() doesn't trigger the calculated property to update.
But I agree - read only is much better.
Thank you, Kai! Do you have any examples where the case-sensitive principle can be used, e.g., with C++ or C# and InterSystems ObjectScript class properties?
Right. So, what is the reason, or if you may, what are the benefits of properties to be case sensitive?
Exactly. And as I mentioned above, you cannot compile such a class with properties that differ only in case. What are the benefits of properties being case sensitive? Don't see any.
How do you mean "use case"? You just shouldn't bother about the case of property names in IRIS while sending a JSON from your frontend to the IRIS REST-API. Like you don't care while sending it vs any SQL engine backend.
Thank you, @Enrico Parisi ! But are you sure about 1.?
I've just created a class:
Class dc.sample.ObjectScript
{
property Name As %String;
property name as %String;
}}
And have a compilation error:
ERROR! In class 'dc.sample.ObjectScript' Property 'Name' from 'dc.sample.ObjectScript' and 'name' from 'dc.sample.ObjectScript' have the same name but differ in case.
Thank you, @Ashok Kumar Thangavel ! I went to submit an idea to fix this, and found your's one :) Voted.
Yes, thank you, AI. But I want it not to care about the case completely.
A yet another workaround for non-obvious caveat of using %JSON.Adapter and JSON transport around persistent data is a necessity to add an ID related property to your persistent class, like PersonId in this case:
Property PersonId As %Integer [ Calculated, SqlComputeCode = { set {*}={%%ID}}, SqlComputed ];This will allow to export ID of a record in DB automatically.
Same when you do updates with records, you need to remove this PersonId JSON from an update request, .e.g like this:
set personDynObj= {}.%FromJSON(person.Read())
do personDynObj.%Remove("PersonId") // Remove PersonId if it exists, as it is calculated
set sc = personObj.%JSONImport(personDynObj)
set sc = personObj.%Save()The simplest way to programmatically create a database in IRIS is:
do $SYSTEM.SQL.Execute("CREATE DATABASE MYDB")And 3 parameters for the spec class that help: HandleCorsRequest - it is most likely CORS will be needed, applicaton/json to support JSON content and ExposeServerExceptions for debug reasons:
Class shvarov.person.spec Extends %REST.Spec [ ProcedureBlock ]
{
Parameter HandleCorsRequest = 1;
Parameter CONTENTTYPE = "application/json";
Parameter ExposeServerExceptions = 1;
...also I always add the same _spec GET endpoint to let swagger have a working specification in docker - the default one doesn't work in docker as IRIS default spec one overrides the host variable to one, that doesn't work.
ClassMethod GetSpec() As %DynamicObject
{
set specname=$p(..%ClassName(1),".impl")
Set spec = {}.%FromJSON(##class(%Dictionary.CompiledXData).%OpenId(specname_".spec||OpenAPI").Data)
Set url = $Select(%request.Secure:"https",1:"http") _ "://"_$Get(%request.CgiEnvs("SERVER_NAME")) _ ":" _ $Get(%request.CgiEnvs("SERVER_PORT")) _ %request.Application
Set spec.servers = [{"url" : (url)}]
Quit spec
}Thanks @Daniel.Pasco. This is what I used in the example class.
Yes, it's great that we have it now in IRIS.