-
Notifications
You must be signed in to change notification settings - Fork 3k
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.
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
Remove all growls on NewDot #13229
Comments
I believe these growls were intentionally left during the Offline API refactors project. The notion being to :do-nothing: as the redirects will go away as we bring those features into NewDot as we progress with reunification. CC: @robertjchen |
Ok, removed from the list! |
Assigning this to myself, as part of my mentorship this year is to be working towards fixing E/app issues. If this becomes an urgent priority please let me know. |
Nice, I'm glad we have a project for this. For what it's worth, I would also remove this one from the list. It's ridiculously far out and something we fix post-reunification.
|
Not overdue, have been OOO from a family emergency. Going to dig into this over the next week. |
Nice, this is a pretty good polish project that's worth picking up now. Happy to help with any questions. |
Thanks Jason! I have a draft PR up with the first growl removed, going to plug away at the rest this week! Should I still hold off on "Error downloading a wallet statement"? |
Oh cool! That's awesome, I don't personally think removing that is an issue since the wallet statement is still a beta, though @joekaufmanexpensify can jump in and confirm one way or another. |
Just for my own understanding, would we be replacing the growl with a different style of error message? Or just removing the growl and leave it failing silently for now? I think either way is fine for now (since no one is really using the statement right now). Although if we aren't adding a new error now, I'll add this to the existing statements cleanup issue we have (which is on hold right now). |
Removing the HOLD from this! |
@joekaufmanexpensify Yeah we'd replace the growl with a different message style. |
Sounds good! Yeah if we're replacing the growl with a different error message style, that sounds great. |
Just for my own understanding, have we decided what will be added in their place? |
Agree with @luacmartins |
Makes sense, ty! |
Is adding in the new indicator messages something I should do as a part of this issue, or will it be covered later? Just clarifying because the scope of the OP was very limited to removing growls. |
Sorry what's the new indicator messages? |
I think @kadiealexander is talking about the new error messages we'd put in place instead of the growl? |
Gotcha, hmm yeah I think we need the error messages to appear somewhere, if we are deprecating the growls where they appear today, right? Apologies if I'm missing something obvious. |
Yea, I agree |
Okay! The OP is very limited to removing the current growls, thanks for the added context. I'm going to pause on actioning this while I figure out the new messaging for these. A few aren't errors, so I'm not sure if any sort of "success" message should be put in place instead. Not an error, need to determine what message to show (if any):
Growl errors to be replaced with
|
Looks like this is ongoing still @kadiealexander, is that right? No rush at all on my end |
Agree that there is no rush, though is would still be good to do this in the intermediate term. I think we don't have many growls as it is. |
@conorpendergrast, @kadiealexander, this Monthly task hasn't been acted upon in 6 weeks; closing. If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead. |
I've discussed this with my mentor @puneetlath and we agreed that the addition of different indicators blew this out of my realm of expertise. I'm unassigning so that this is not blocked on me. |
@puneetlath @kadiealexander This still needs to be internal, correct? |
Wrong Puneet! From everything I saw this could be external, but I could be wrong. |
Oh that's embarrassing, silly me |
Agreed, seems like it can definitely be external. If it's a little more involved, it could be a good one for an expert agency. |
@puneetlath Do you think you could update this with everything it needs to be external? |
@conorpendergrast, this Monthly task hasn't been acted upon in 6 weeks; closing. If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead. |
On hold for WAQ focus
As identified in this issue and discussed in this thread, we have some remaining growls that are now out of style. This is not a bug, but still needs to be fixed. @luacmartins found the following that still have growls:
And we should remove them all.
The text was updated successfully, but these errors were encountered: