Greg Dennis

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.

JsonSchema template JSON generation

2

Given a schema, create example JSON for use as a template.

Currently the scrolling settings allow me to always capture the scroll events or not. When always capturing, the page doesn't scroll at all when scrolling with the mouse over the...

I was looking through the code to figure out how you build a general package and language specific packages. I just happened upon the `hy` (Armenian) nuspec file and saw...