Skip to content
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

To Do list: list structure #1

Merged
merged 12 commits into from
Sep 29, 2022
Merged

To Do list: list structure #1

merged 12 commits into from
Sep 29, 2022

Conversation

NahnahAJ
Copy link
Owner

Project Requirements

  • Set up a new project with webpack that is based on the webpack exercise you have already completed.

  • Create an index.html file and write your HTML markup here. Create an empty To Do List placeholder (<div> or <ul> element). The index.html file must be set as a template using the HTML Webpack Plugin.

  • Create an index.js file and set an array of some simple to do tasks (array of objects). Each task object should contain three keys:

  1.     description [string].
    
  2.      completed [bool].
    
  3.        index: [number].
    
  • Write a function to iterate over the tasks array and populate an HTML list item element for each task.

  • On page load render the dynamically created list of tasks in the dedicated placeholder. The list should appear in order of the index values for each task.

  • Create a style.css and set rules for the To Do List. CSS must be loaded by Webpack Style/CSS Loader. Your list should be a clone of the part of the minimalist project captured in the video below.

  • All your source files (index.html, index.js and style.css) must be located in /src directory and your distribution files will be generated by webpack and served by webpack dev server from /dist folder.

Copy link

@roshan-bajgain roshan-bajgain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @NahnahAJ,

Good job so far!
There are some issues that you still need to work on to go to the next project but you are almost there!

Highlights

  • No linter errors. ✔️
  • GitHub flow is followed. ✔️
  • PR has a good title and summary. ✔️

Required Changes ♻️

Check the comments under the review.

Optional suggestions

Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.

Cheers and Happy coding!👏👏👏

Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.


As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

Comment on lines 2 to 22
{
string: 'Complete to do list project',
boo1: 'Join stand-up Call',
id: '1',
},
{
string: 'Join stand-up Call',
boo1: 'Not completed',
id: '2',
},
{
string: 'Arange a call',
boo1: 'Join stand-up Call',
id: '3',
},
{
string: 'Control the teams project',
boo1: 'Join stand-up Call',
id: '4',
},
];

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • According to the requirement, you need to set an array of some simple to-do tasks (array of objects). Each task object should contain three keys. that is: description [string], completed [bool], index: [number]. Please make it like this.
    const tasks = [ { description: 'An example description in string', completed: false, index: 10, }, ];

Comment on lines 10 to 13
<div class="container">
<span><input type='checkbox'>${element.string}</span>
<div><i class="fa-solid fa-ellipsis-vertical"></i></div>
</div><hr>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • I would suggest you please make sure to populate the HTML list item element for each task. You have populated the string but make sure to populate the completed [bool]. For reference:
    <p>${completed ? 'completed' : 'not completed'}</p>`;

README.md Outdated
Comment on lines 18 to 36

To get a local copy up and running follow these simple example steps.

### Prerequisites

- Have a Desktop or Laptop Computer running on with Windows, Mac OS or Linux operating system.
- Have git installed on the Computer
- Have a browser install on the Computer

### Setup

- If it suits you, on your local computer, create a directory in your preferred location (e.g in the Desktop or Document directory)

### Install

- Open your Terminal/Powershell or any command line interface you use, then navigate to your created above directory or the directory you'll like to clone this project directory.
- Type `https://github.com/NahnahAJ/To-Do-List.git` if your're using https with git or `git@github.com:NahnahAJ/To-Do-List.git` if your preferred is ssh and hit enter.
- Navigate to the `To-Do List` directory on your local computer in your above chosen directory and open the `src/index.html` file.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • I would suggest you please make sure that you write the proper step to run the project on the machine.
    For example, You need to do npm install then only you have to do npm start to start the project. please write those step

Copy link

@KayLemba KayLemba left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Status: Approved ✔️
Hi @NahnahAJ

Your project is complete! Great job for making the requested changes🥇. There is nothing else to say other than... it's time to merge it 🍾🚢 :shipit: . Congratulations! 🎉💯🌟

Good Points 👍

  • Descriptive Pull Request
  • No linter errors

Cheers..Happy coding!..and keep soaring higher! 💻 🍷 🚀
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

As described in the Code reviews limits policy you have 2 more limited reviews per this project. If you think that the code review was not fair, you can request a second opinion using this form.

@NahnahAJ NahnahAJ merged commit 0705433 into main Sep 29, 2022
@NahnahAJ NahnahAJ deleted the list-structure branch September 29, 2022 07:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants