Greg Dennis

Split into multiple libraries by function

3

The different functionalities (data model, serialization, schema, path, pointer, & transform) are all fairly disjoint as far as internal dependencies. I wonder if I should split out the libraries based...

Many libraries return line number and position along with parsing errors. I never thought this was necessary since I have a pointer that indicates where the error is, but the...

Schema analysis

1

If be nice to be able to have a schema analyze to ensure its logically sound. For example, is the `minimum` less than the `maximum`, or is the `default` valid...

Inspired by [this SO question](https://stackoverflow.com/q/59811315/878701), having additional requirements of generated types could prove useful. ```c# TypeGenerator.AddRequirement(); ```

So, while working on a personal project, I found some things that may be nice to have for serialization that could be supported well by attributes. Of course, these would...

JsonLogic

1

http://jsonlogic.com/ May be worth doing.

http://jsonata.org/ This is an alternative to JSON Path. Looks fairly similar, but the feature set is more extensive. There's also not a .Net implementation as yet.

Support for JSON5

4

This would include support for things like BSON and comments. Ideally, I'd like to update the parser system to allow for injection of sub-parsers from external code. This would mean...

JsonPath should support returning a list of expanded paths to the results instead of just the list of results. This would apply to operators that can return more than one...

Serialization and deserialization needs better error reporting, as is implemented in the parsing process.