Skip to content
New issue

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

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom

The Compromise library should be updated automatically #115

Open
ProfJanetDavis opened this issue Jan 7, 2020 · 0 comments
Open

The Compromise library should be updated automatically #115

ProfJanetDavis opened this issue Jan 7, 2020 · 0 comments
Labels
software quality Software qualities not visible to end users. Refactoring, testing, internal documentation, etc.

Comments

@ProfJanetDavis
Copy link
Collaborator

Sometime after resolving #114, look into whether the Compromise dependency can be updated automatically through npm or GitHub.

Note that Compromise must be distributed as part of the Chrome extension, unlike other npm dependencies which are used only for testing.
@ProfJanetDavis ProfJanetDavis added the software quality Software qualities not visible to end users. Refactoring, testing, internal documentation, etc. label Jan 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
software quality Software qualities not visible to end users. Refactoring, testing, internal documentation, etc.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ProfJanetDavis