Indeed with the current way JSON streaming is handled, optional values are not considered. This needs more work and the issue is tracked here https://github.com/arjanadriaanse/pascal-language-server/issues/7 [1].
Regards, Arjan [1] https://github.com/arjanadriaanse/pascal-language-server/issues/7 On Fri, 24 Apr 2020 16:10:47 +0700 Ryan Joseph via fpc-pascal <fpc-pascal@lists.freepascal.org> wrote: > > On Apr 24, 2020, at 3:59 PM, Arjan Adriaanse <ar...@adriaan.se> > > wrote: > > > > FPCDIR="/usr/lib/fpc/3.2.0/source" > > LAZARUSDIR="/usr/share/lazarus" > > I see now! I didn't know that but it's easy to document once we get > that far. > > btw, I'm having a problem with the fact that published un-set > properties are being set with null values. Some of the fields are > marked as optional in the protocol and returning a NULL value could > be an error which crashes the client. I don't have much experience > with streaming RTTI so I don't know how to resolve this. > > For example this "documentation" property will always be set to null > but really what want is to omit the key entirely. > > published > property documentation: TMarkupContent read fDocumentation write > fDocumentation; > > > Regards, > Ryan Joseph > > _______________________________________________ > fpc-pascal maillist - fpc-pascal@lists.freepascal.org > https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
pgps4WKflU_bC.pgp
Description: OpenPGP digital signature
_______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
