[Matt Ha Interview] Todo List implementation#13
Open
matthaaa wants to merge 18 commits intoevery-io:mainfrom
Open
[Matt Ha Interview] Todo List implementation#13matthaaa wants to merge 18 commits intoevery-io:mainfrom
matthaaa wants to merge 18 commits intoevery-io:mainfrom
Conversation
This file contains hidden or 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
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.
Overview
This branch implements a Todo List app with tasks organized into status columns (To Do, In Progress, Done). Users can create and move individual tasks. The state is managed centrally, and
localStorageis used as a lightweight persistence layer.Features and Considerations
Buttoncomponent)localstorageservice later for data operations; this allows data to be persisted without connecting to a backend server, but also decouples data management from UI, enabling easy swapping to a backend API if it were to be implemented in the future.ChallengeComponentand flows down via props in order to maintain a single source of truth; this simplifies debugging, and avoids issues like state duplication across multiple components.Additional features
I was admittedly having fun with this, so I added some more features for demonstrative purposes (also to showcase the scalability of the
taskServicefile):Future considerations
Screenshot
Reviewers:
@barrypeterson
@jmatusevich
@falecci
@danfsd