moogle-cc / email Goto Github PK

There should be a permanent bucket where all emails on which we are bcc-ed are save

The current version is too slow and buggy.

Repro steps:

1. Log in to moogle.cc/email/
2. Check developer console
   Expected: emails should appear in inbox
   Actual: No emails are shown and a message appears in developer console that "Quota has been exceeded"

Test setup: FF 87 on desktop with factory defaults. Same error happens even after clearing cache or in Incognito/Private mode.

Potential fix is to migrate to IndexedDB as explained here @ https://stackoverflow.com/questions/58604583/quotaexceedederror-the-quota-has-been-exceeded-progressive-web-app-offline-mo

1. log in to email
2. go to neelesh bucket
3. open the solitary email
4. click reply-all

Expected: I should be able to reply-all to both [email protected] and [email protected]
Actual: [email protected] is not included

• Make the logo of MOOGLE smaller.
• Make the ellipse which contains the number of mails smaller.
• Make the shadow of nav bar lighter.
• Make the shadow lighter of the div on which the mail is displayed
• Make the heading of the particular mail Bold
• Date should be of #3F3F3F color
• Make icons of comment, reply and link smaller
• When a mail is selected it should be highlighted with shadow of #000000 color with blur 16 and border radius 11

1. Ask Affan to reply-all to an email
2. Ask him what he sees in the FROM email

Expected: it should say [email protected]
Actual: it will show Affan's Gmail id because that is what he used to sign up on Cognito.

Resolution:

1. If the id_token contains a field called cognito:username, use that as the email id. So the FROM email will be value_of_cognito:username@domain.tld
2. If id_token only contains email, split the email on @ and use the first part as the email id. So the FROM email will be `[email protected]

Right now, we can't see

1. when the email was received
2. which Moogle email ID received the email
3. who else was copied on the email

At a minimum we should show this information.

In addition, we should also consider showing email size and an icon for attachments

Use an editor that is not heavy for the system to proess

Implement new email design made by Naina.

1. Refresh should run every five minutes
2. User must be notified of a new email on server using a dismissable UI element like a Toast. The Toast should stay until the user dismisses it.
3. The user should be asked to reload the email list.

Right now, the commenter name is editable so anyone can impersonate anyone as the commenter. This field should not be directly editable.

Change the colour of post excerpt to #3F3F3F in the right panel.

There should be space in the underline of the word BLOG in the nav bar.

Right now, we only show the most recent 70 mails. Add a load more feature.

The FROM email is hardcoded fo @moogle.cc regardless of the domain on which the emails are being read.

The senders email domain should be the same as the domain on which the emails are being read.

Use /moogle/email/comments as endpoint. Note the plural form of comment.

1. Include a comments box alongside every received email
2. Comment box should support markdown
3. Comments should be associated with an email

BCC yourself on all emails

Email attachments must be downloadable from the browser.

The circle which contains number of emails should be smaller circles.
The bar which comes when a particular email is selected should have lighter shadow and less border radius.
Change the icons of reply, comment and link and make them even smaller and give proper spacing between the icons.

Right now, when a new email is being composed, the FROM email is empty. We should always show a FROM address.

Right now, the names of buckets are only driven by the TO addresses.

1. Add a separator between spam and the rest of the buckets
2. Show count of emails in each bucket
3. Show read/unread state of emails
4. Sort buckets alphabetically
5. Include an All bucket containing all emails from all buckets
6. Add grey background to the comments section to distinguish it from the rest of the email

1. log in to Moogle/email
2. have an email open
3. click on reply in that email
4. cancel the compose window
5. click on the new email button

Expected: the compose window should not have TO/CC pre-filled since we are trying to send a new email
Actual: TO/CC fields have some existing values

1. Send an email to [email protected] where this email is in CC with some other non-moogle email in TO
2. Check the bucket names on moogle.cc/email

Expected: email should be placed in Tests bucket
Actual: a new bucket is created with the name based on TO email and the email is placed in that bucket

This happens when we are cc-ed or bcc-ed on email, The logic to create new buckets fails with a undefined exception

Axios POST request should pass the request body using data as the key.

See link for reference: https://stackoverflow.com/questions/51415439/how-can-i-add-raw-data-body-to-an-axios-request#51415585