> On Aug 7, 2020, at 9:09 PM, Michael Van Canneyt
> wrote:
>
> try
>B:=Not Assigned(FOnRestoreProp);
I just rebuilt the compiler (couldn't figure out how to recompile just the
fpc-json package) and got the new changes but there seems to be a regression
and I'm not getting anything deser
On Fri, 7 Aug 2020, Ryan Joseph via fpc-pascal wrote:
On Aug 7, 2020, at 8:31 PM, Michael Van Canneyt wrote:
An option to allow nulls to be detected and handles would of course be a nice
addition.
For the time being, you can just set jdoIgnorePropertyErrors on the destreamer
options.
> On Aug 7, 2020, at 8:31 PM, Michael Van Canneyt
> wrote:
>
> An option to allow nulls to be detected and handles would of course be a nice
> addition.
>
> For the time being, you can just set jdoIgnorePropertyErrors on the
> destreamer options.
Quick check right now and setting that optio
On Fri, 7 Aug 2020, Ryan Joseph via fpc-pascal wrote:
On Aug 7, 2020, at 7:58 PM, Michael Van Canneyt wrote:
By itself, fpJSON of course allows null values.
What are you using as a serialization technologgy ?
I didn't write the serialization layer and this is my first time using the FP
> On Aug 7, 2020, at 7:58 PM, Michael Van Canneyt
> wrote:
>
> By itself, fpJSON of course allows null values.
>
> What are you using as a serialization technologgy ?
I didn't write the serialization layer and this is my first time using the FPCs
RTTI system for this purpose. Having said th
On Fri, 7 Aug 2020, Ryan Joseph via fpc-pascal wrote:
I'm trying to get the pascal language server working on Visual Studio Code and
during testing I found that sending null values to the server is causing
problems. i.e.:
...
"processId": 3997,
"clientInfo": {
"name": "vscode",
I'm trying to get the pascal language server working on Visual Studio Code and
during testing I found that sending null values to the server is causing
problems. i.e.:
...
"processId": 3997,
"clientInfo": {
"name": "vscode",
"version": "1.47.3"
},
"rootPath": null
