Project

General

Profile

Actions

Defect #2254

closed

Use the same json format as npm in package json desciptors.

Added by Radek Tomiška almost 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Low
Assignee:
Radek Tomiška
Category:
Continuous development
Target version:
Start date:
05/14/2020
Due date:
% Done:

100%

Estimated time:
Affected versions:
Owner:

Description

When product is released by IdM tool usage, then frontend package.json descriptors are formated differently, than after 'npm install' command. The result of this issue is commit like this:
https://github.com/bcvsolutions/CzechIdMng/commit/25aaea3d20dd5e8a1308ef1b6349e4e120dbf341#diff-d63bc29359e705db86ff2eb9ac3cfa72

Prevent to create these changes in IdM tool.

Actions #1

Updated by Radek Tomiška almost 4 years ago

  • Status changed from New to In Progress
Actions #2

Updated by Radek Tomiška almost 4 years ago

  • Status changed from In Progress to Needs feedback
  • Assignee changed from Radek Tomiška to Vít Švanda
  • % Done changed from 0 to 90

I configured the same json format used for update frontend module version as by npm.

Commit:
https://github.com/bcvsolutions/CzechIdMng/commit/8cb5c2ae25a5811dc3b9e28d7f224d970cb7d185#diff-9af11bcf4e5d18a9287599e05ac8f88a

Could you provide me a feedback, please?

Actions #3

Updated by Vít Švanda almost 4 years ago

  • Status changed from Needs feedback to Resolved
  • Assignee changed from Vít Švanda to Radek Tomiška
  • % Done changed from 90 to 100

I did review and tested it by local change of the product version. After that I use gulp install ... no additional change were made. Thanks for that.

Actions #4

Updated by Radek Tomiška almost 4 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF