Skip to content

[Marika-Daniel] - code review #17

@Paing-Ko

Description

@Paing-Ko

README

[Does the README describe the project using the subheadings: Why?, What?, How? i.e. Why have you created this repo, what does it do, how does it do it?]

Still a work in progress

User stories

[Does the project meet the user stories for that week?]

we believe so, but it is better if user can check it off

Learning outcomes

[Does it demonstrate the learning outcomes for that week?]

Yes, but test.js need to be updated

UI bugs

[Can you see any obvious bugs or areas to improve?]

if user can add task using keyboard (with enter key)
or can edit

Instructions

[Does everything work as expected or were there missing instructions?]

Readme.md is not finished yet

File structure

[When you open the project in your editor, does the file structure make sense?]

Yes

Flow of control

[ Can you you follow the different paths the code might take?]

Yes

Naming

[Do variables and functions have clear and descriptive names?]

Yes

Readability

[Do you understand the code?]

Yes

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions