-
Notifications
You must be signed in to change notification settings - Fork 163
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
Added subscription to folders #622
Conversation
I appreciate your work on this, but I think we should have discussed this a bit more :)
|
"we should have discussed this a bit more" Indeed, we could have a process to ask more questions beforehand. (Ex.: will a merge request on XYZ be accepted? How would you prefer we do Y?) But a lot of things we start don't necessarily get finished soon after. Priorities shift. And some of the developers are in training. So the risk is that we'd open up a lot of discussions, and that many of them lead nowhere. It's more important that we optimize your time. So I am quite OK that the discussion starts on a merge request. This means the junior developer has a good grasp of the challenge, and a fruitful discussion can ensue. And please do feel comfortable in asking for major changes to a MR. The devs are in training and this is a great way for them to learn. Thanks! |
That is definitely an overkill IMHO. I think Jason simply meant that the effort put into this PR could be better focused if a few things got first described in words instead of code as describing in words would probably be sufficient for understanding and would take less time and less effort for the author 😉. I for myself find it actually mostly better to "show the code" as soon as possible as that completely eliminates misunderstandings which are often the major source of delays in implementation of features. |
Hello @jasonmunro. I pushed a new commit. Please check. |
Looks like we have some conflicts here that need to be resolved before re-checking. Thanks! |
2e1c269
to
60c2d17
Compare
Already resolved. Thanks. |
60c2d17
to
44a39a1
Compare
I think Jason's comments were addressed but there are a few functionality issues. Let's solve them and then we can merge. |
44a39a1
to
f8babb1
Compare
Hello @kroky I made changes. |
f8babb1
to
1f17151
Compare
1f17151
to
4d2ab60
Compare
4d2ab60
to
f98f689
Compare
@kroky can you check please, I fixed some issues :
|
All looks good to me but it needs some extensive testing. I might be able to do it after the holidays. |
Hello @kroky. Any update on this ? |
It still seems a bit shaky. I see + LSUB in the folder list now which doesn't have any children. I also go to manage folders, create a new test folder under INBOX, manage to move emails in and out. Then, turn on show only subscribed folders. I don't see the test one anymore. I go to manage folders, settings icon on the top right, clicked the checkbox of test folder. I still don't see it in the list. Reloaded the folder list but I don't see it. Now I can't go to subscribed folders anymore. I go to manage folders, click the top right hand side cog icon, it redirects to cypht home page. Something's wrong here. |
Also, please make sure you merge latest master into this branch, so you can actually test against the .env and other enhancements there. |
d84c465
to
b08cb7f
Compare
b08cb7f
to
a029114
Compare
Thanks @kroky Can you check again. I took in account everything you reported here. But one thing I found is that when create a folder by default it is unsubscribed. |
Pullrequest
Add support for IMAP folder subscriptions
Issues