[UXPROD-3356] Lotus release - Spring way compliance Created: 04/Oct/21  Updated: 02/Mar/22  Resolved: 02/Mar/22

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Lotus (R1 2022)

Type: New Feature Priority: P3
Reporter: Oleksandr_Dekin Assignee: Unassigned
Resolution: Done Votes: 0
Labels: back-end, epam-spitfire
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
defines MODNOTES-206 `notes` property is not included in G... Closed
is defined by FAT-1134 Adjust Karate tests for mod-notes (No... Closed
is defined by MODNOTES-193 Extend search functionality by ignori... Closed
is defined by MODNOTES-198 Spring way: rename module name to NOTES Closed
is defined by MODNOTES-199 Spring way: error during calculate notes Closed
is defined by MODNOTES-204 Missing attributes in api response Closed
is defined by MODNOTES-205 Changing note type returns 500 code Closed
is defined by MODNOTES-208 Fix jar name in Dockerfile Closed
is defined by STSMACOM-612 Notes > Handle /note-links response w... Closed
Relates
relates to FAT-1113 Adjust Karate tests for mod-notes Closed
relates to MODNOTES-180 Restructuring of the project structure Closed
relates to MODNOTES-181 Migrate models from RAML to Swagger Closed
relates to MODNOTES-182 Migrate SQL scripts to liquibase Closed
relates to MODNOTES-183 Change logic for NoteTypes Closed
relates to MODNOTES-184 Change logic for NoteLinks and Notes Closed
relates to MODNOTES-185 Rewrite tests for NoteTypes Closed
relates to MODNOTES-186 Rewrite tests for NoteLinks Closed
relates to MODNOTES-187 Rewrite tests for Notes Closed
relates to MODNOTES-188 Implement ExceptionHandler for custom... Closed
relates to MODNOTES-189 Verify mod-notes according to spring way Closed
relates to MODNOTES-192 Calculate note type usage and include... Closed
Front End Estimate: Out of scope
Back End Estimate: XXL < 30 days
Development Team: Spitfire
PO Rank: 0

 Description   

Overview: To migrate module from Vertx to Spring way.

 

Feature:

  • Migrate module mod-notes (https://github.com/folio-org/mod-notes) from Vertx to Spring way
  • Change structure folders and pom.xml (Include lib folio-spring-base), Rewrite DeploymentDescriptor-template.json and ModuleDescriptor-template.json by using spring format ("srvcId": ""@artifactId@-@version@"), change Dokerfile and Jenkins for Spring way = 3 SP
  • Rewrite all models from raml to swagger API, change controller layer (samples, json, controller) = 5 SP
  • Move all sql scripts to liquibase (change schema, remove jsonb, create ENTITY) Delete RMB scripts: https://github.com/folio-org/mod-tags/blob/master/src/main/resources/db/changelog/changes/v1.0.0/_cleanup-rmb.xml = 5 SP
  • Change logic for NoteTypesImpl (dao, service, controller, create default note type) = 3 SP
  • Change logic for NoteLinksImpl.java and NotesImpl.java (dao, service, controller) = 8 SP
  • Write tests (eliminate vertx from tests):
    • Tests for NoteTypesImpl = 3 SP
    • Tests for NoteLinksImpl = 3 SP
    • Tests for NotesImpl = 3 SP
  • Change logic from custom exceptions to @ExceptionHandler = 2 SP
  • Verify logic mod-notes on the snapshot (after merging Spring way into master) = 1 SP

 

 



 Comments   
Comment by Khalilah Gambrell [ 14/Oct/21 ]

Oleksandr_Dekin and there is no UI work?

Comment by Oleksandr_Dekin [ 14/Oct/21 ]

Khalilah Gambrell no, only back-end

Comment by Natalia Zaitseva [ 29/Nov/21 ]

Due to discussion with Pavlo Smahin changed fix version field for all included issues to 3.0.0

Generated at Fri Feb 09 00:31:22 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.