Clean up dependencies and isolate into features

[chipsenkbeil]

vimwiki

• Core: language components and utilities like LocatedComponent, Region, and Point
• Features:
  • "parse": expose the parsers module and include dependencies like nom
  • "serde": derive serde serialize & deserialize on components
  • "juniper": derive juniper graphql object on components (some may need custom definitions, scalars, etc)
    • NOTE: No custom scalar is needed for NaiveDate, but a custom feature on juniper is needed
    • NOTE: If we go the scalar route for uriparse's URI, we'd need to make a newtype wrapper as described in https://github.com/graphql-rust/juniper/issues/429
  • "locate": add module that has ability to transform an LC<Page> into an rstar tree where we can query for a component by line & column
    • NOTE: Would also expose ability to walk up the tree. For instance, finding a list item and walking up to the list, etc.
  • "tag-graph": add module that has ability to extract a graph of tags to parent components using petgraph
    • NOTE: Tag is hashable and can be converted to a string, so we want the graph to be able to search by tag, string, and &str
  • "convert-json": add method to LC that does serde_json's to & from json
  • "convert-html": add method to LC that converts to html
  • "debug-timekeeper": add our timekeeper code for context (and include lazy_static dep)

vimwiki_macros

• Core: produce rust code to construct components

vimwiki-server

• Core: graphql server endpoint (juniper, warp, and clap deps)
• "watch": Watches a directory for changes and automatically re-loads those files (notify)
• "multi-threaded": Supports multi-threaded execution of parsers (tokio workers for pages); may need something like this or "async" in vimwiki crate for parsers

[chipsenkbeil]

Closing out as this is being done differently.