Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support seeding for JSON POCOs
See original GitHub issueI’m trying to use a POCO mapping (to use a jsonb column with a list of a defined object). When I try to run a migration I get an error:
Cannot scaffold C# literals of type ‘System.Collections.Generic.List`1[Api.Models.UserType]’. The provider should implement CoreTypeMapping.GenerateCodeLiteral to support using it at design time.
Small project to reproduce the issue: WebApplication2.zip
The only way I’ve found to achieve this is to create a String and make the JsonSerializer.Serialize() by myself wich is not the best solution at all.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:9
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
As this may go well together with the general push for JSON support in EF Core, I’ve put this in the 6.0 milestone - but I wouldn’t say this is the highest-priority item…
This is currently unsupported; if you use JSON POCO mapping, you’ll have to take care of seeding yourself.
The type mapping could use reflection to discover public properties which are readable and writable, and generate the proper C# code based on that. This will probably require some additions to code generation on the EF Core upstream side.