Skip to content

Conversation

@Samathingamajig
Copy link
Collaborator

@Samathingamajig Samathingamajig commented Jun 9, 2025

Screen.Recording.2025-06-08.at.11.38.35.PM.mov

This change is Reviewable

@DereC4
Copy link
Member

DereC4 commented Jun 16, 2025

Is storing the email itself in optionsStore a good idea?

@Samathingamajig
Copy link
Collaborator Author

Is storing the email itself in optionsStore a good idea?

seems like the best place to put it without making a separate store just for it, open to other thoughts.

maybe a userDataStore? but I can't really think of other kinds of things we'd need for that.

a boolean for whether to save the email is probably an "option", and it makes some sense to me to keep the email data nearby. Don't want to overload the types to be false for not storing and string when storing, that is too confusing

@DereC4
Copy link
Member

DereC4 commented Jun 18, 2025

Is storing the email itself in optionsStore a good idea?

seems like the best place to put it without making a separate store just for it, open to other thoughts.

maybe a userDataStore? but I can't really think of other kinds of things we'd need for that.

a boolean for whether to save the email is probably an "option", and it makes some sense to me to keep the email data nearby. Don't want to overload the types to be false for not storing and string when storing, that is too confusing

hm mayb idk it could be a good setup for any future things that need to be stored

@Samathingamajig
Copy link
Collaborator Author

Is storing the email itself in optionsStore a good idea?

seems like the best place to put it without making a separate store just for it, open to other thoughts.
maybe a userDataStore? but I can't really think of other kinds of things we'd need for that.
a boolean for whether to save the email is probably an "option", and it makes some sense to me to keep the email data nearby. Don't want to overload the types to be false for not storing and string when storing, that is too confusing

hm mayb idk it could be a good setup for any future things that need to be stored

i guess

Copy link
Member

@Razboy20 Razboy20 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally, code changes look good to me. (still need to test as a build though).

Let's remove 'rememberMyEmail' as a setting stored in options, and rather infer this from whether an email is saved or not.

If a user decides to unselect remember my email, then unset email in options store.

showCalendarSidebar: await OptionsStore.get('showCalendarSidebar'),
showUTDiningPromo: await OptionsStore.get('showUTDiningPromo'),
rememberMyEmail: await OptionsStore.get('rememberMyEmail'),
emailAddress: await OptionsStore.get('emailAddress'),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If an email is set, can we not consider this to be indicative of the email being remembered? Think 'rememberMyEmail' could be removed.

@Samathingamajig
Copy link
Collaborator Author

will look into this @Razboy20

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants