Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

New UD Annotatrix logo #386

Open
wants to merge 891 commits into
base: dev
Choose a base branch
from
Open

New UD Annotatrix logo #386

wants to merge 891 commits into from

Conversation

Persevere04
Copy link

Ggtee

Kevin Murphy and others added 30 commits August 21, 2018 12:16
Fix table view deleting words
Fix pressing enter disabling navigation
Fix table view not showing dependencies
Fix Autocomplete box width
This way, we don't need to run the compiler independently -- we can
just execute the TypeScript files as if they were JavaScript!
The file referenced doesn't even exist anymore :^)

IMO, we don't need this key anyway, since we don't expect anyone to
use us as a library.. that wouldn't really make sense.
We're always just storing our corpora as JSON, so we don't need any
of this sqlite logic.

In the future, I could imagine it might be interesting to add this
back in, but I think it's better not have to maintain this dead code
in the meantime...
Since `client/` and `server/` are now consuming this project directly
as TypeScript, we don't have a separate build step anymore.
We don't want to make all this random data available in the browser
at runtime...
Functionally, this is equivalent to what we had before, but it makes
it a little easier to share the code into the final bundle (otherwise
the fact that `notatrix` was its "own project" led to annoying errors
with `babel`/`browserify` that didn't seem worth solving...).
Now, this works correctly:

    $ npm run test
@github-pages github-pages bot temporarily deployed to github-pages August 22, 2022 01:04 Inactive
Rather than crashing the whole application, we can just avoid any
files in `corpora_path` that we don't know how to parse.  Obviously,
this isn't great if the file was corrupted somehow (but does contain
data we'd like to keep)...

Tested this by running

    $ cat > corpora/issue506.json
    {"hello":

    $ npm run server  # before
    SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at /home/kevinmurphy/src/jonorthwash/ud-annotatrix/src/server/list-treebanks.ts:51:55
    at Array.map (<anonymous>)
    at /home/kevinmurphy/src/jonorthwash/ud-annotatrix/src/server/list-treebanks.ts:48:34
    at FSReqCallback.oncomplete (fs.js:192:5)

    $ npm run server  # after
    Failed to parse corpora/issue506.json: SyntaxError: Unexpected end of JSON input

Closes #506.
@github-pages github-pages bot temporarily deployed to github-pages October 22, 2022 19:59 Inactive
@github-pages github-pages bot temporarily deployed to github-pages November 20, 2022 17:02 Inactive
@jonorthwash jonorthwash temporarily deployed to github-pages October 27, 2023 19:58 — with GitHub Pages Inactive
@jonorthwash jonorthwash temporarily deployed to github-pages October 27, 2023 20:06 — with GitHub Pages Inactive
@jonorthwash jonorthwash temporarily deployed to github-pages October 27, 2023 20:16 — with GitHub Pages Inactive
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.