Closed vinaybadgujar102 closed 2 months ago
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Updated (UTC) |
---|---|---|---|
zinzen | ✅ Ready (Inspect) | Visit Preview | Sep 1, 2024 10:31am |
Yes this is nice. If you can, add the new goal 'pling' sound when restoring the goal.
done
@tijlleenders Please check the delete functionality again :) @vinaybadgujar102 can you please try collab again now. I've updated the PR
Previously deleting a goal was taking too long because of the sound.
@tijlleenders what are you expecting in that case ? isn't that a natural behavior ?
@Tushar-4781 The same behavior as when it would be in 'done'. This is currently working for root goals - but not for subGoals.
The use case is if you mark something as done - then change your mind. You don't want to have to navigate away first.
@Tushar-4781 the dot is correctly disappearing now after accepting changes according to your comment. Additionally I encountered some bugs related to share functionality for which I will create issues once I confirm them.
When I complete multiple goals in Daily routines then select the circle on one of them, nothing happens.
@tijlleenders, I fixed this in latest commit.
@vinaybadgujar102 I think there's a more efficient way to handle this. Since the component already has access to the length of the goals, it might be better to use that directly rather than passing it in as props
@tijlleenders, I agree. Creating tests for core features will help minimize redundant efforts in fixing regressions introduced by new changes.
@tijlleenders can we have test in seperate pr
@tijlleenders can we have test in seperate pr
Yes, of course.
I noticed now that crossing out a done item and then deleting an item will move the done item to done while moving the deleted to trash.
I would expect only the deleted item moving to trash, and the done being crossed out untill you navigate away and back again.
@vinaybadgujar102 are u fixing it or do you want me to fix it ?
@vinaybadgujar102 are u fixing it or do you want me to fix it ?
It would be helpful if you fix this.
Holding off on 'fixing' this as state update exceptions on default React get complicated.
resolves #1991