-
Notifications
You must be signed in to change notification settings - Fork 102
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
WIP on ultralist 2.0 #245
Draft
gammons
wants to merge
12
commits into
main
Choose a base branch
from
ultralist-2.0
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
WIP on ultralist 2.0 #245
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is a WIP on v2.0 of ultralist. The main goal of this is to bring a higher level of professionalism and structure to the project as a whole. This will be achieved by: 1. **Splitting concerns into packages.** There will be a core `ultralist` pacakge, which will implement the main business logic around Todo lists, todos, recurrence, etc. 2. **Eliminate dependence on CLI.** Ultralist will eventually have a more tui-like user interface, and there are a lot of places in the app that have a reliance on ultralist being a CLI only. Separate the concerns of CLI interaction into a `cli` package to prepare for that. 3. **Proper use of errors**. Improve error handling across all packages. 4. **Prepare for a re-think of the backend + syncing.** Ultralist should use a store like CouchDB for syncing. Prepare the app for that eventuality.
With point 2, would that mean there is no way to use it as a simple CLI anymore? Or will there be the CLI interface and the TUI interface? |
@tcassaert there will be both! None of the existing functionality will go away. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a WIP on v2.0 of ultralist.
The main goal of this is to bring a higher level of professionalism and
structure to the project as a whole. This will be achieved by:
Splitting concerns into packages. There will be a core
ultralist
pacakge, which will implement the main business logic around Todo lists, todos, recurrence, etc.Eliminate dependence on CLI. Ultralist will eventually have a more tui-like user interface, and there are a lot of places in the app that have a reliance on ultralist being a CLI only. Separate the concerns of CLI interaction into a
cli
package to prepare for that.Proper use of errors. Improve error handling across all packages.
Prepare for a re-think of the backend + syncing. Ultralist should use a store like CouchDB for syncing. Prepare the app for that eventuality.