highlighting

We should create custom error types for when we parse the TaskType, and TypeStatus in our FromStr implementations. The same applies to the IndexUid::new method that returns an IndexResolverError, we should implement the right IndexResolverError::from for a custom error type too.

It would be much more Rust idiomatic and easier to work with.

We have [a String error for the

You can see this in the examples on the public demo page.

null/true/false should be literals, but instead are keywords:
![CleanShot 2022-05-12 at 14 20 01](https://user-images.githubusercontent.com/3127419/1

Woops! Sorry for that, and thank you for catching it! I meant to type continue there but I slipped. Testing the codebase on the demo directory did not raise problems so I went along.

No promises here, but would you be open to PRs related to building an integration test suites? Such regressions could be caught pretty easily with basic tests.

_Originally posted by @clement-elbaz in ht