#322 Deserializing applicationmetadata keeps unmapped properties

[tjololo]

Description

Fixes #322

Related Issue(s)

• ApplicationMetadata in app-lib should allow unmapped properties on root level #322

Verification

• Your code builds clean without any errors or warnings
• Manual testing done (required)
• Relevant automated test added (if you find this hard, leave it and we'll help out)
• All tests run green

Documentation

• User documentation is updated with a separate linked PR in altinn-studio-docs. (if applicable)

[ivarne]

If we need to support newtonsoft json, there should probably be a test for it.

Also, the important thing to test here is the round trip deserialization - serialization. I don’t think we actually care much about accessing unknown properties through the dictionary.

[tjololo]

If we need to support newtonsoft json, there should probably be a test for it.

Also, the important thing to test here is the round trip deserialization - serialization. I don’t think we actually care much about accessing unknown properties through the dictionary.

While trying to create tests for newtonsoft I realised that supporting newtonsoft would result in a different json returned if serializing with system.text and deserializing with newtonsoft (JsonElement vs JToken) as we still plan to remove Newtonsoft in favor of System.Text I don't think it is worth the effort to support both when we are using System.Text.Json to deserialize the file in AppMetadata.cs

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

100.0% Coverage
0.0% Duplication