Skip to content

Remaining work before general release #1

Description

@bishopb

DoD: As a contributor, I understand how to build and develop the application locally. As a general user, I understand how to download and run it locally. As a sponsor, I am able to login to https://keepass-web.app with my Github profile and then connect my Google drive and then open my file for read/write, without errors.

  • Cleanup docs so that contributors and users have a clear understanding
  • Document how the pages work together
  • Block on disabled branch protection rules
  • Block on code quality issues (i.e., CodeQL, any issue)
  • Ensure code coverage report shows 100% on all packages / pages
  • Ensure build pipeline creates signed releases and pushes to GitHub Pages
  • Add support for routing
  • Add support for Google Drive
  • Ensure all common workflows are supported:
    • New database, open database, save database, lock database, close database
    • Login with master password, Login with key file
    • Toggle password visibility
    • Generate password
    • List entries, group entries, search entries
    • Add entry, edit entry, trash entry, recover entry, delete entry
    • Store UUID, icon, title, username, password, URL, notes, tags, created date-time, modified date-time, expiration date-time
    • Add attachment, rename attachment, remove attachment
    • Table view on a group, with double click to copy
  • Show code version on every page
  • Add support for 3.1 version, as only 4.x is supported on 0x67
  • Add support for logging in as a GitHub sponsor
  • Warn when leaving with unsaved changes
  • Apply design consistently
  • Fix blockers
    • Google cloud frame is too small in Chrome on MacOS
    • Double footer on Google Chrome page
    • Canceling in cloud goes back to index page in frame instead of 0x67; should unframe and return to cloud top
    • Distinguish secret visibility icon based on mode (show/hide)
    • Default to table view
    • favicon.ico
  • Mobile aware version
  • Framing reuse
  • Key file from cloud
  • Optimize download size
    • Create an e2e test suite that covers the full paths
    • Optimize the obvious: duplicate code reduction, excessive comments, etc.
    • Aggressively optimize: algorithms, etc.
  • Ensure a11y
  • Adversarial review
  • Review copy, ensure use cases are documented
    • KDBX on USB stick
    • Local download, no Google
    • Local download, with Google (python3 -m http.server 57277)
    • Kiosk use
  • Setup parked artifacts #2

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions