Closed 1hitsong closed 2 months ago
This pull request has merge conflicts. Please resolve the conflicts so the PR can be reviewed. Thanks!
So, what's our path forward on this one? It feels like cewert and I are currently at an impasse on both the code and refresh approach.
To make the most informed comment, I would need to test this PR and really dig in to the code. As it stands from a quick overview, it looks like the update is written, and might only need some possible comments as it is.
As it is an enhancement, would it not be possible to merge this and then discuss code standards later? If it turns out there is more to address, it could continue to be enhanced at a later point.
There have been a lot of changes across the client apps and client app teams to enhance the speed/velocity of releases, we shouldn't block that further.
Sorry for lack of response. Feel free to dismiss my review if needed.
As it is an enhancement, would it not be possible to merge this and then discuss code standards later? If it turns out there is more to address, it could continue to be enhanced at a later point.
This is tagged as bugfix which means after it's merged it will be in prod for the next bugfix release. I think that's where the disconnect is coming from because I was reviewing this PR as if it were being pushed to prod after merging. We wouldn't be able to enhance it until the next minor release.
To recap my thoughts:
isFirstRun
in previous bugfixes and I believe we should use it here too. If the team decides enums are better, then I think that should be a separate enhancement PR that converts all views to use enums isntead of isFirstRun
.I too see this as a bug fix, not as an enhancement.
My apologies, I was using "enhancement" in the general sense to mean "improvement", and not in the context of any programming or project management methodology.
This pull request has merge conflicts. Please resolve the conflicts so the PR can be reviewed. Thanks!
Closing in favor of #1771
Changes
Issues
Fixes #1647