SchemaObject | Iterate over a MySQL database schema as a Python object | Database library

It was an issue with Swagger UI.

Fixed in Swagger UI 4.5.0 and Swagger Editor 4.0.7.

Should have dug a little harder on my own before asking the question. Anyhow, I managed to figure it out. For a little setup, I don't use realm entities directly in my application, I actually convert those entities on the way out to DTOs. My DTO's all implement an interface that defines a method to get the property object for insert/update operations. Previously I was typing that return object to be Partial when in fact I should have been using RealmInsertionModel.

Hopefully this will be of some help to someone else.

Having the field value disappear just means that the custom field was not correctly implemented. When the system can't select/persist a record or a field it disappears when control focus is lost.

The DAC field type appears to be wrong. Usually string list uses small codes of about 2 or 3 letters string with fixed size: [PXDBString(3, IsFixed = true)]

Since you are setting the list dynamically you don't need to define null string values in the DAC: [PXStringList]

You need to make sure that your event is always providing the expected code values. This can be checked by removing the conditions and using constants for the SetList method call: https://stackoverflow.com/a/38089639/7376238

Maybe you missed some steps like creating the field in the database table. You can test with an unbound PXString field instead of a PXDBString like in this example to see if that's the issue: https://stackoverflow.com/a/49907964/7376238

There are two possible reasons:

1. MyUtils.staticSchema returns null or
2. AnotherClass is initialized during the initialization of MyClass due to a cyclic dependency.

I assume that you've already verified/ruled out option #1 so I'll focus on the second one:

Non-trivial static field initialization that depends on other classes can be problematic, because it can introduce long dependency chains and even dependency loops in class initialization.

If class A calls a method of class B during class initialization and class B calls a method of class A during class initialization, then there's a loop: that means that some code will see half-initialized classes.

If your MyClass somehow (directly or indirectly) touches AnotherClass during class initialization then it's quite possible tha the call to MyClass.getStaticSchema() is actually executed before schemaObj is initialized.

The best solution is to make the class initialization of any class depend on as few classes as possible.

Simple sample demonstrating the problem:

The contents provided by the toString() method is some convenience feature for the developer. It does not necessarily produce valid JSON representation of the object. You should use a JSON serializer to serialize your JAVA object into a JSON string. This can for example be done with the help of the Gson library.

It's importing from the index.ts file

Imagine next structure:

There are multiple things that are preventing you from getting the correct result. First when you do const schema: Schema = { ... } you actually loose the type information about literal strings. The solution is to remove : Schema annotation (as it looses type information) and use as const for the literal, or use a special identity function who's job is to capture literal types.

Next thing is that you have to make type property mandatory on your schema otherwise all properties are optional making any type match the schema, so you can not do the mapping.

Finally "default" property does not have the correct type for objects, so you need to use conditional types instead. Putting it all together you have this: