openlmis-reference-ui

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Bumped version to 5.1.3-SNAPSHOT

Released reference-ui version 5.1.2

Bumped version to 5.1.2-SNAPSHOT

5.1.2-RC2 release

Bumped version to 5.1.2-SNAPSHOT

5.1.2-RC1 release

done

done

please change String type to all lowercase

please change String type to all lowercase

added

added

done

done

added

added

please add jsdocs

please add jsdocs

I think that this need translation

I think that this need translation

how about some jsdocs?

how about some jsdocs?

done

done

OLMIS-5501: Updated report-ui version

Yeah, I forgot about that. Could you advise me if those changes should treat as a patch or minor change?

Yeah, I forgot about that. Could you advise me if those changes should treat as a patch or minor change?

What about a... CHANGELOG.md? https://review.openlmis.org/static/ogdo0b/2static/images/wiki/icons/emoticons/biggrin.gif

What about a... CHANGELOG.md?

I am still waiting for correct URLs to reports

I am still waiting for correct URLs to reports

OLMIS-5501: Created scaffold for superset reports
OLMIS-5501: Created scaffold for superset reports
OLMIS-5354 Update referencedata-ui to 5.5.0-SNAPSHOT

Added .vscode to the .gitignore

What really is important are the changes in the dev-ui repository and package.json in the rest (which is repeated across all other modules), npm-shrinkwrap.json and yarn.lock files are generated. T...

What really is important are the changes in the dev-ui repository and package.json in the rest (which is repeated across all other modules), npm-shrinkwrap.json and yarn.lock files are generated. The change we're introducing here is locking dev-ui dependencies, which are no longer fetched to the node_modules in the root directory, but instead, are fetched into node_modules/dev-ui/node_modules. What we're doing is moving them to the node_modules directory so they are available to the module that is relying on dev-ui, lack of them there would break the build process because of missing dependencies. For yarn.lock we're basically copying the one generated in the .tmp directory, which is where we're firing yarn up during the build process. If you have any concern, please let me know.

These changes are virtually impossible to review in-depth.

These changes are virtually impossible to review in-depth.