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

Notably v1.4 Deliverables (By 13-04) #380

Closed
34 of 48 tasks
kevinputera opened this issue Apr 5, 2020 · 0 comments
Closed
34 of 48 tasks

Notably v1.4 Deliverables (By 13-04) #380

kevinputera opened this issue Apr 5, 2020 · 0 comments
Assignees
Labels
priority.High Must do status.Ongoing The issue is currently being worked on. Note: remove this label before closing an issue. type.Enhancement An enhancement to an existing story
Milestone

Comments

@kevinputera
Copy link

kevinputera commented Apr 5, 2020

Deliverables for each person for v1.4 milestone (please finish before code-related by Friday 10/04, documentation/code quality/logging by 13/04 midnight!)

@AY1920S2-CS2103T-W17-2/developers :

  • Create a v1.4 release
  • Release a v1.4 JAR

@firzanarmani :

@johannagwan :

  • Move responseText to ViewStateModel
  • Create TestUtil class to remove code duplication for the test cases for:
    • Sug Cmds
    • Sug Cmd Parsers
    • Sug Engine Impl
  • Improve test cases
  • More comprehensive error message to the user
  • Search Sug Cmd Parser (“searching for keyword: …)
  • Add shorthands for Sug Commands and Sug Engine Impl
  • Update Sug Cmd Parsers to pass a list of results to the sug commands
  • For all commands: integrate user input into the message. E.g. “Create new note entitled …”
  • Improve code quality
    • Search Sug Cmd
  • UG typo ([PE-D] Typo in UG #357, [PE-D] Incorrect parsing for edit command #366)

@ljiazh3ng :

  • More comprehensive error message to the user(Using responseText)
  • Improve code quality on test case(Same as Jo)
  • Add parser DG
  • Improve path’s explanation in DG
  • Logic method for editing block’s content (for edit modal)
  • Disable case-sensitivity in path, update UG to reflect this ([PE-D] Auto suggestion/correction not working as expected #351)

@HemanshuGandhi :

  • Implement Edit Display Modal***
    • Separate Title and Body sections.
  • Enable Enter (Tab) selection of Suggestions Items**
    • Make sure suggestion items are traversable using arrow keys directly from inside command input
  • Hide "Root"
  • Improve UI for Response text
  • Bug Fix: disable click event on sideBar.
  • Improve UI. In particular, color theme and suggestion Items
  • Add path to block content display view (see b)
  • UI Test cases/assertions/Defensive Programming/logging
  • Update View diagram in DG (Ui.png, with cleaner lines)
  • UG: guide user through experience of editing a note.

@kevinputera :

  • Fix bugs in correction engine’s forward matching feature (Fix forward-matching inverted bug #333, Fix forward-matching inexact matching bug #388)
  • Make correction engine returns a list of results (if there are multiple possibilities with the same distance)
  • Move out CorrectionEngine dependency to Parser’s and SuggestionEngine’s level, rather than CommandParser’s and SuggestionCommandParser’s level.
  • Improve logging across CorrectionEngine and Compiler
  • Improve test coverage of Compiler
  • Improve DG’s explanation on correction engine + markdown spec
  • Improve UG’s explanation on correction engine + markdown compiler
  • Work on my PPP (portfolio)
  • Finish up Markdown to HTML compiler
  • Work on demo for correction engine (need to clearly separate the role of suggestion engine/parser from correction engine) + markdown compiler
@kevinputera kevinputera changed the title Notably Notably v1.4 Deliverables (By 31-03) Apr 5, 2020
@kevinputera kevinputera changed the title Notably v1.4 Deliverables (By 31-03) Notably v1.4 Deliverables (By 13-04) Apr 5, 2020
@kevinputera kevinputera added priority.High Must do status.Ongoing The issue is currently being worked on. Note: remove this label before closing an issue. type.Enhancement An enhancement to an existing story labels Apr 5, 2020
@kevinputera kevinputera added this to the v1.4 milestone Apr 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority.High Must do status.Ongoing The issue is currently being worked on. Note: remove this label before closing an issue. type.Enhancement An enhancement to an existing story
Projects
None yet
Development

No branches or pull requests

5 participants