Tom MacWright

Simplified namepaths: dropping 'inner', using JS syntax for instance members

1

Namepaths are [a JSDoc'ism](http://usejsdoc.org/about-namepaths.html) - a feature that documentarians use to refer to different parts of their exported API. Their examples: ``` myFunction MyConstructor MyConstructor#instanceMember MyConstructor.staticMember MyConstructor~innerMember // note that...

Type syntax

2

There are essentially 3 type syntaxes at play: - JSDoc - TypeScript - Flow documentation.js supports JSDoc and Flow, but as we've painfully discovered, JSDoc and Flow are very different....

Names in GEDCOM look like `John /Smith/`. We should include a parser to make it easier to show a chart with the last name _not_ in slashes.

GEDCOM has a fancy date format that can express uncertainty. This project could include a parser of it. See also the Extended DateTime format https://github.com/sfomuseum/go-edtf

The tokenizer I've written is "one token per line", so it's not quite a real tokenizer. It would be useful, if we want to emit nice errors, to actually record...

Right now, this throws on unknown pointers. That isn't a viable strategy for the long run, and will break on a test of all fixtures.

Integrate OAuth endpoint into this repo

4

Ideally, we use [parcel as middleware](https://github.com/parcel-bundler/parcel/issues/355#issuecomment-353806604) and have one command that builds and serves the frontend _and_ handles authentication.

- [x] Drag interaction - [x] Recognize file type - [ ] Ask about append / replace? - [x] Multiple files?