Closed HarelM closed 1 year ago
Some links to things that should just work, but don't: https://github.com/dotnet/runtime/issues/1566 https://github.com/NetTopologySuite/NetTopologySuite.IO.GeoJSON/issues/44 https://github.com/NetTopologySuite/NetTopologySuite.IO.GeoJSON/issues/117
Current status: The build is not failing, but there are a lot of runtime issues due to changes in deserialization...
Things to test and fix:
There is an issue with the OSM id that is used as string in the server side and as number in the client side. Newtonsoft was able to handle this gracefully but STJ fails. This is currently in ShareUrl and MapLayerData POCOs. https://stackoverflow.com/questions/59097784/system-text-json-deserialize-json-with-automatic-casting
This was solved by last commit b3e8144ded186e0b7c5847c79fa8cc5336a4af47. I haven't seen any other issues lately. If new issues arise I will open different issues and solve them as they come.
What is the problem this feature will solve?
Moving to STJ might improve the site's performance and reduce dependencies
What is the feature you are proposing to solve the problem?
Infta change
What alternatives have you considered or tried?
Keep the current state
Additional information
No response