Hi VSCode users!

Just want to check with you, is this settings.json file ideal enough if I:

1. Want VSCode to connect to IRIS in docker?

2. Want to use VSCode SQL Tool?

The connection settings file:

Hi Developers!

Recently we discussed the naming convention on packages we deploy and even made some choices.

Here I want to have a conversation on the naming convention for unit tests.

Of course, we wish every good library has unit tests. Here is the documentation and some good articles(one, two, three) regarding it on the Developer Community.

Let's decide on the naming of UnitTests packages?

The suggestion is that unit test classes will all start with the UnitTest package name.

E.g. if your library's class name is:

johndoe.lib.class

The related unit test class will be:

UnitTest.johndoe.lib.class

What about folders?

The suggestion is that unit test classes will live separately from source classes, e.g. in /tests directory.

Here is the example of a repository with unit tests that are named and placed according to the proposal.

What do you think?

Hi Developers!

How do you handle errors with &sql a.k.a. embedded SQL?
I think I found a universal error-handling template which works in any situation:

&sql(SELECT * FROM Sample.Person)

if SQLCODE < 0 throw ##class(%Exception.SQL).CreateFromSQLCODE(SQLCODE,"Context description")

What is your choice?

Hi Developers!

Here're the technology bonuses for the FHIR programming contest that will give you extra points in the voting:

• FHIR Server REST API usage 
• The usage of SQL Schema of FHIR Resources 
• Healthcare standards data transformation
• Docker container usage

See the details below.