GithubHelp home page GithubHelp logo

cs2103-ay1819s1-w14-4 / main Goto Github PK

View Code? Open in Web Editor NEW

This project forked from nus-cs2103-ay1819s1/addressbook-level4

0.0 4.0 4.0 26.8 MB

:clipboard::shopping_cart: Inventory Manager Application

Home Page: https://cs2103-ay1819s1-w14-4.netlify.com/

License: MIT License

Shell 0.20% Java 99.22% CSS 0.55% HTML 0.04%
java javafx junit asciidoc software-engineering nus izone red-velvet

main's Introduction

Inventory Manager

Build Status Build status Coverage Status Code Quality

Ui
  • This is a desktop Inventory Management application. It has a GUI but most of the user interactions happen using a CLI (Command Line Interface).

  • It is a Java application which aims to help supermarkets' stakeholders to manage the inventory.

  • It is written in OOP fashion. This will enable the application to model the supermarket realistically and help stakeholders to manage the inventory smoothly.

Acknowledgements

Licence : MIT

main's People

Contributors

zhiyuan-amos avatar darren96 avatar yamgent avatar fzdy1914 avatar zulq9 avatar damithc avatar pyokagan avatar yao-tx avatar esmondtan avatar m133225 avatar mightycupcakes avatar yamidark avatar rinder5 avatar limmlingg avatar eugenepeh avatar chao1995 avatar vivekscl avatar yl-coder avatar lejolly avatar pierceandy avatar ndt93 avatar edmundmok avatar kychua avatar okkhoy avatar alexlmeow avatar lixiaoooowei avatar verylazyboy avatar nicholaschuayunzhi avatar cheec avatar jia1 avatar

Watchers

James Cloos avatar  avatar  avatar  avatar

main's Issues

Feedback on week 10 project progress

Subject: feedback on week 10 project progress

See mid-v1.3 progress guide for more details of the activities mentioned below.

Team progress

Recommended progress for v1.3

  • Milestone v1.3 managed systematically
    • A suitable deadline set (:heavy_check_mark: well done!)
    • Issues allocated to it e.g., link (:heavy_check_mark: well done!)
  • A new jar file has been released on GitHub (:exclamation: try to do by next milestone)

Individual progress of @darren96

Recommended progress for v1.3

  • Has issues/PRs assigned for the milestone (:heavy_check_mark: well done!)

Individual progress of @EsmondTan

Recommended progress for v1.3

  • Has issues/PRs assigned for the milestone (:heavy_check_mark: well done!)

Individual progress of @zulq9

Recommended progress for v1.3

  • Has issues/PRs assigned for the milestone (:heavy_check_mark: well done!)

Individual progress of @fzdy1914

Recommended progress for v1.3

  • Has issues/PRs assigned for the milestone (:heavy_check_mark: well done!)

Individual progress of @yao-tx

Recommended progress for v1.3

  • Has issues/PRs assigned for the milestone (:heavy_check_mark: well done!)

Tutor: @nhs-work

Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2018-10-24 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.

Feedback on week 7 project progress

Subject: feedback on week 7 project progress

See v1.1 progress guide for more details of the activities mentioned below.

Team progress

  • Team org and repo set up correctly (:heavy_check_mark: well done!)
  • PR created from team repo to AB-4 (:heavy_check_mark: well done!)
  • Auto-publishing set up for the team repo (:heavy_check_mark: well done!)
  • README page:
    • Ui.png has been updated (:heavy_check_mark: well done!)
  • User Guide: some content has been updated (:heavy_check_mark: well done!)
  • Developer Guide: some content has been updated (:heavy_check_mark: well done!)
  • Team repo git tagged as v1.1 (:heavy_check_mark: well done!)

Individual progress of @darren96

  • Used forking workflow:
    • Created PRs (:heavy_check_mark: well done!)
    • Reviewed PRs (:heavy_check_mark: well done!)
  • Merged updates to documents (:heavy_check_mark: well done!)
  • Merged changes to java/fxml (:exclamation: try to do by next milestone)
  • darren96.png uploaded and linked from AboutUs page, merged (:heavy_check_mark: well done!)

Individual progress of @EsmondTan

  • Used forking workflow:
    • Created PRs (:heavy_check_mark: well done!)
    • Reviewed PRs (:heavy_check_mark: well done!)
  • Merged updates to documents (:heavy_check_mark: well done!)
  • Merged changes to java/fxml (:exclamation: try to do by next milestone)
  • esmondtan.png uploaded and linked from AboutUs page, merged (:heavy_check_mark: well done!)

Individual progress of @zulq9

  • Used forking workflow:
    • Created PRs (:heavy_check_mark: well done!)
    • Reviewed PRs (:heavy_check_mark: well done!)
  • Merged updates to documents (:heavy_check_mark: well done!)
  • Merged changes to java/fxml (:exclamation: try to do by next milestone)
  • zulq9.png uploaded and linked from AboutUs page, merged (:heavy_check_mark: well done!)

Individual progress of @fzdy1914

  • Used forking workflow:
    • Created PRs (:heavy_check_mark: well done!)
    • Reviewed PRs (:heavy_check_mark: well done!)
  • Merged updates to documents (:heavy_check_mark: well done!)
  • Merged changes to java/fxml (:heavy_check_mark: well done!)
  • fzdy1914.png uploaded and linked from AboutUs page, merged (:heavy_check_mark: well done!)

Individual progress of @yao-tx

  • Used forking workflow:
    • Created PRs (:heavy_check_mark: well done!)
    • Reviewed PRs (:heavy_check_mark: well done!)
  • Merged updates to documents (:heavy_check_mark: well done!)
  • Merged changes to java/fxml (:exclamation: try to do by next milestone)
  • yao-tx.png uploaded and linked from AboutUs page, merged (:heavy_check_mark: well done!)

Tutor: @nhs-work

Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2018-10-03 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.

Undo/Redo/Clear: Everyone can run undo/redo/clear on forbidden list

Now, users can undo and redo even the changes on approving / rejecting po and user management regardless of roles. Same as Clear Command too.

Eg:
If user A is an admin and made some changes on staff list and approving po, then he logged out without exit the program.
User B logged in as a user. He will able to undo/redo the changes from previous user. He is also permitted to clear the whole inventory.

Feedback on week 9 project progress

Subject: feedback on week 9 project progress

See v1.2 progress guide for more details of the activities mentioned below.

Team progress

Recommended progress for v1.2

  • Issue labels set up e.g., type.*, priority.* (:heavy_check_mark: well done!)
  • Milestones created: v1.4 v1.3 v1.2 [Please ensure milestones are setup until 'v1.4'] (:heavy_check_mark: well done!)
  • Some issues marked as type.Story e.g., link (:heavy_check_mark: well done!)
  • Some issues prioritized using priority.* labels e.g., link (:heavy_check_mark: well done!)
  • Milestone v1.2 managed systematically
    • A suitable deadline set (:heavy_check_mark: well done!)
    • Issues allocated to v1.2 e.g., link (:heavy_check_mark: well done!)
    • All issues/PRs in it are closed/merged. (:exclamation: try to do by next milestone)
    • Milestone closed (:exclamation: try to do by next milestone)
    • Code tagged as v1.2 (:heavy_check_mark: well done!)
  • Build passing (:heavy_check_mark: well done!)
  • Some issues assigned to milestone v1.3 e.g., link (:heavy_check_mark: well done!)

Not graded:

  • Updated User Guide for v1.2 (:+1: Kudos!)

Individual progress of @darren96

Recommended progress for v1.2

  • Merged updates to java/fxml files (:heavy_check_mark: well done!)
  • Merged updates to the Developer Guide (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the next milestone (:heavy_check_mark: well done!)

Individual progress of @EsmondTan

Recommended progress for v1.2

  • Merged updates to java/fxml files (:heavy_check_mark: well done!)
  • Merged updates to the Developer Guide (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the next milestone (:heavy_check_mark: well done!)

Individual progress of @zulq9

Recommended progress for v1.2

  • Merged updates to java/fxml files (:heavy_check_mark: well done!)
  • Merged updates to the Developer Guide (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the next milestone (:heavy_check_mark: well done!)

Individual progress of @fzdy1914

Recommended progress for v1.2

  • Merged updates to java/fxml files (:heavy_check_mark: well done!)
  • Merged updates to the Developer Guide (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the next milestone (:heavy_check_mark: well done!)

Individual progress of @yao-tx

Recommended progress for v1.2

  • Merged updates to java/fxml files (:heavy_check_mark: well done!)
  • Merged updates to the Developer Guide (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the next milestone (:heavy_check_mark: well done!)

Tutor: @nhs-work

Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2018-10-17 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.

Feedback on week 8 project progress

Subject: feedback on week 8 project progress

See v1.1 progress guide for more details of the activities mentioned below.
Mid-milestone progress reports are FYI only. They are not graded.

Team progress

Recommended progress for the upcoming milestone

  • Issue labels set up e.g., type.*, priority.* (:exclamation: try to do by next milestone)
  • Milestones created: v1.2 v1.3 v1.4 [Please ensure milestones are setup until 'v1.4'] (:heavy_check_mark: well done!)
  • Issues marked as type.Story e.g., link (:heavy_check_mark: well done!)
  • Some issues prioritized using priority.* labels e.g., link (:heavy_check_mark: well done!)
  • Milestone v1.2 planned
  • A suitable deadline set (:exclamation: try to do by next milestone)
  • Issues allocated to v1.2 e.g., link (:heavy_check_mark: well done!)
  • Issues allocated to v1.3 e.g., link (:heavy_check_mark: well done!)
  • Build passing (:heavy_check_mark: well done!)

Individual progress of @darren96

Recommended progress for the upcoming milestone

  • Merged updates to java/fxml files (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the next milestone (:heavy_check_mark: well done!)

Individual progress of @EsmondTan

Recommended progress for the upcoming milestone

  • Merged updates to java/fxml files (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the next milestone (:heavy_check_mark: well done!)

Individual progress of @zulq9

Recommended progress for the upcoming milestone

  • Merged updates to java/fxml files (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the next milestone (:heavy_check_mark: well done!)

Individual progress of @fzdy1914

Recommended progress for the upcoming milestone

  • Merged updates to java/fxml files (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the next milestone (:heavy_check_mark: well done!)

Individual progress of @yao-tx

Recommended progress for the upcoming milestone

  • Merged updates to java/fxml files (:heavy_check_mark: well done!)
  • Has issues/PRs assigned for the next milestone (:heavy_check_mark: well done!)

Tutor: @nhs-work

Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2018-10-10 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.

Feedback on week 6 project progress

Subject: feedback on week 6 project progress

See mid-v1.1 progress guide for more details of the activities mentioned below.

Team progress

Progress noted (well done! ๐Ÿ‘):

  • Team org and repo set up with the correct names.
  • PR created from team repo to AB-4.

Suggestions (to do soon):

None

Individual progress of @darren96:

Progress noted (well done! ๐Ÿ‘):

  • Team repo forked to your GitHub account.
  • PRs created to update documents.

Suggestions (to do soon):

  • Create PRs to do a local change to the Java code.

Individual progress of @EsmondTan:

Progress noted (well done! ๐Ÿ‘):

  • PRs created to update documents.

Suggestions (to do soon):

  • Fork team repo to your GitHub account.
  • Create PRs to do a local change to the Java code.

Individual progress of @zulq9:

Progress noted (well done! ๐Ÿ‘):

  • Team repo forked to your GitHub account.
  • PRs created to update documents.

Suggestions (to do soon):

  • Create PRs to do a local change to the Java code.

Individual progress of @fzdy1914:

Progress noted (well done! ๐Ÿ‘):

  • PRs created to update documents.
  • PRs created to update Java code.

Suggestions (to do soon):

  • Fork team repo to your GitHub account.

Individual progress of @yao-tx:

Progress noted (well done! ๐Ÿ‘):

  • Team repo forked to your GitHub account.
  • PRs created to update documents.

Suggestions (to do soon):

  • Create PRs to do a local change to the Java code.

Tutor: @nhs-work

Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 18/9/2018 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.

Bug: Clear Command clears the staff data

Clear Command should not be clearing the staff data to be empty which will cause no account for user to login. To prevent this, clear command should restore the staff list to default state only.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.