go to post Evgeny Shvarov · Aug 12 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?
go to post Evgeny Shvarov · Jul 25 Thank you, @Jonathan Lent ! Pleasure to hear we are still better in some spaces than bots :)
go to post Evgeny Shvarov · Jul 25 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.
go to post Evgeny Shvarov · Jul 25 Great example of custom class queries, @Timothy Leavitt ! I wonder if the recursion with ..AllFetch() is necessary here and in every case?
go to post Evgeny Shvarov · Jul 18 Very useful article, a lot of use-cases and examples! Thank you @Ashok Kumar T !
go to post Evgeny Shvarov · Jul 12 Exciting initiative! I think this line in Update is "orphaned": set myobj = ##class(%Library.DynamicObject).%FromJSON(%request.Content)
go to post Evgeny Shvarov · Jul 10 @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.
go to post Evgeny Shvarov · Jul 3 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.
go to post Evgeny Shvarov · Jul 3 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.
go to post Evgeny Shvarov · Jul 1 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.
go to post Evgeny Shvarov · Jul 1 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?
go to post Evgeny Shvarov · Jun 30 Right. So, what is the reason, or if you may, what are the benefits of properties to be case sensitive?
go to post Evgeny Shvarov · Jun 30 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.
go to post Evgeny Shvarov · Jun 30 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.
go to post Evgeny Shvarov · Jun 30 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.
go to post Evgeny Shvarov · Jun 30 Thank you, @Ashok Kumar T ! I went to submit an idea to fix this, and found your's one :) Voted.
go to post Evgeny Shvarov · Jun 29 Yes, thank you, AI. But I want it not to care about the case completely.
go to post Evgeny Shvarov · Jun 27 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()
