seanwash/msgbox-app

MsgBox is a tool for viewing the contents of msg files.

MsgBox App

MsgBox is a tool for viewing the contents of msg files. Currently, it allows you to:

• Import unlimited msg files
• View attachments contained in import msg files
• Search the contents of imported msg

This project is still in early alpha/proof of concept stage and is not to be considered stable. To see what's in the works, you can view the Beta Project.

msgbox-app's Issues

Replace indexed-db usage with sqlite

• Get some sort of sqlite to work
• Place DB in app.getPath('userData') so that data persists across installs
• Update import fn to write to the new DB
• Update inbox listing to pull from the new DB
• Update show view to pull from the new DB
• Remove react-indexed-db altogether
• Research a migration strategy in case future migrations are required to work with the data
• Setup data serialization/deserialization to convert to/from JSON

Swap tailwind CDN link out for postcss plugin

Create attachments table, save attachments to disk when a message is imported.

Message tagging

Read markers

When searching, the entire sidebar is re-rendered and only the message list itself should re-render.

Note to self, pay close attention to the message count below the search input.

How can we make sure that data is not totally wiped when using a new build?

Update asset storage to separate assets into folders named by their message's ID.

Note that to do this we'll need to generate the attachment's ID ahead of time, maybe using the cuid lib or similar.

Date Filter

Be able to organize in ascending/descending order by date

Highlight message in sidebar when selected

Dev only debug menu for updating the database, toggling read status, etc.

Convert electron side to typescript

It seems like we will need two totally separate build chains here, one for building the electron side and one for building the react side.

Failed import notices

It would be nice for jaime to have a list of file names that failed to import

Extract renderer IPC calls so that they're not inline with the react query usage

Delete attachments when their message is deleted

When archiving the selected message, the message view should empty

Add app wide drag/drop for adding new files

Todo

• Add app wide drag/drop
• Files should auto import when dropped onto the app

Resources

https://github.com/streamich/react-use/blob/master/docs/useDrop.md

Move parsing of files to the electron side

Decide if this will stay OSS, add appropriate license if so.

Investigate indexedDB usage with react-indexedd as there seem to be some performance issues

Add delete message feature

• Icon in mesage list
• Clicking icon should remove item from indexed db

Integrate tailwind based design

I'm thinking that we can riff off of this https://tailwindui.com/components/application-ui/page-examples/detail-screens

Search by subject, sender, recipient

Extract app IPC calls

Wrap renderer ipc calls in react query

Is this doable, or does it even make sense to do?

---

The main goal here would be to abstract away the IPC communication into reusable hooks that are wrapped with react-query. The goal behind using react-query is to have a totally uniform interface for working with any of the app's data, and I think having the querycache available would be usefull too.

Setup & configure eslint

extends: ["plugin:@typescript-eslint/recommended"]

Update fetchAllMessages to accept limit/offset paging

Infinite message list scrolling

Create app icon

Allow a user to keep their own notes on messages

App can sometimes request a msg that has been deleted

I believe this stems from the msg id stored as the selected message.

Persist the currently selected message

Will need to store a record into the DB somewhere when a message is selected, and then on boot we'll want to pull it out and then dispatch selectMessage if there's a value.