-
Notifications
You must be signed in to change notification settings - Fork 13
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
Beta Feedback #15
Comments
As for the data model, I must say I was slightly surprised to see a new Since you mentioned a11y review, I also noticed that there's no close button on the settings/account dialog, and you can't close it with Esc. But nice job! |
Hey @Vinnl, thanks for your feedback, as always :D.
Yeah, this is part of what I want to improve when I say "Container choice". Besides letting people choose, I also want to think about better defaults. Initially, I thought it'd be fine to have containers in the root because I don't think people is going to have many workspaces (though who knows). But now, I'm leaning more towards putting everything inside The real problem, though, is how to call the default workspace 😅. The idea is that you would have one workspace for each part of your life (Work, Household, Hobbies, etc.), and in the previous version of the app I explicitly ask users to name their workspaces. But here, I wanted to remove friction so the initial workspace is created automatically (you can rename it later). And the name I'm using for this default workspace is "Main", which I probably took from git's default branch name nowadays. But I'm not super happy with that choice :/. So I'm all ears for suggestions, because so far I haven't been able to come up with something better. I guess I'll also do some research to see what other apps do.
Thanks for mentioning that. I'm actually using Headless UI, so In my other apps, I have close buttons in modals. But here, I wanted to remove as much clutter from the UI as possible, in line with the "focus" theme. I even pondered having a "focus mode", but in the end I think the default UI is pretty minimal already :D. Though maybe I overdid it a bit 😅. I'll reconsider adding the close buttons, even after fixing the |
I think |
I'm finding that it occasionally duplicates all my lists (without duplicating their contents) when synchronizing. Edit: For one workspace, it's now duplicating the contents of the lists without duplicating the lists themselves. |
Thanks for reporting this, I've also seen it myself sometimes; and others have mentioned that it also happens in Umai 😱. The problem, though, is that I haven't been able to reproduce it in my development environment :(. I suspect it has something to do with race conditions. I'll definitely look into it more in depth before the final release, but if anyone finds a way to reliable reproduce this, please let me know. |
I have managed to reproduce the sync duplication in Focus with a fresh pod on localhost and only using one browser:
The renaming somehow leads to all tasks in the list to be duplicated. It just adds the same task file with an additional suffix to the container (similar I have seen with recipes in Umai) Network wise it GETs the container, then GETs the task that is in there, and then it tries to GET the task file with the suffix for some reason, fails with 404 and then makes a PATCH to create it. I exported the HAR file (zipped for github upload), you can import it to you browsers network tools for further analysis: This is reproducably duplicating tasks, whenever I rename the list. Notably the renaming does not change the name of the list in my pod, it just duplicates the tasks |
Just noticed on my test pod it also started to duplicate type index for some reason (never had that in my real pod luckily) Here is another network recording that lead to this: For some reason the app seems to decide it needs to create another type index, although the original type index could clearly be fetched. It just randomly adds a new type index to the profile and then creates the file
|
That's awesome @angelo-v, thanks a lot 🙇. I was able to reproduce this in a test, so I'm sure I'll be able to pinpoint the issue now :D. I still haven't been able to reproduce the type index duplication, but I'm sure it must be something similar. I still don't know why this is happening, but that pattern of creating a new document adding a suffix is actually a Soukai mechanism to avoid overriding existing documents. The thing is that this should only happen for creating new documents, not for updates. So there must be something wrong in some part of the code that is trying to execute an update as if it were a new document. |
Some days ago, I deployed a development build of the next version to focus.noeldemartin.com. Please, give it a try!
As I say in the page, though, this is a beta. So beware of using it in production. Here's the parts I consider mostly done:
And here's some things that I already have in the roadmap, and will tackle before the release:
And that's it! If you have some feedback, please leave me know in this issue or contact me in private. If you only care about the final release, you can subscribe to this issue and I'll close it when the beta is over.
Thanks!
The text was updated successfully, but these errors were encountered: