Jhipster updating fake-data csv files after entity updates - jhipster

I just updated my entities via an updated jdl file. After successfully running 'jhipster import-jdl myUpdatedJdl.jdl', I've noticed my csv files under liquibase/fake-data were not updated. Is there an easy way to update my fake-data csv files?

You have to rebuild you project. It should be enough
mvn clean install
or using maven wrapper
mvnw
and check if you still have proper configuration in application-dev.yml file:
liquibase:
# Remove 'faker' if you do not want the sample data to be loaded automatically
contexts: dev, faker
Faker must be there for generating some sample data

Related

How to bundle project config files with parcel

I have created a common utility package which will be used by multiple node applications and for bundling it, I am using parcel which works fine but except one issue.
The common utility package consists of config files, which takes care of loading configuration as per env.
Issue:
While using this common utility package in a nodeapp I get the below error, when i try to run the app:
Error: loggerConfig config variable not found
at Object.n [as getLoggerConfig] (/Users/pm/Documents/example-service/node_modules/common.utils/dist/index.js:14:1037)
So It seems to me, the config files are not bundled along the build files generated.
Help Needed:
Is there a way we can tell parcel to bundle these config files as well?
Please guide me if I am thinking the wrong way.
Thanks in advance.

How to generate JHipster application into a specific directory?

Suppose I modified the source code of generator-jhipster repo and I would like to generate my "custom" JHipster application into a specific directory, how would I accomplish this task?
After installing JHipster:
npm install -g generator-jhipster
I would be able to generate the application with:
jhipster
However, this command runs the application directly from the JHipster repository.
Since I modified the source code, I could generate the application locally by running:
node jhipster.js
in the ../cli directory.
The problem is, running this command in cli directory will generate the application in the same directory (cli) and this is not what I want.
I need to find a way to export the application into a specific directory.
Note: I strongly believe this has something to do with process.cwd(), because that generates the application in the local directory, but I'm not sure exactly
which source file to modify as I don't want to break anything.

mvnw not generating test directory for jhipster 4.10.0

I have deleted the default test directory generated by ./mvnw. Now running maven doesn't generate test repository no more. I need some help please

Install a node package without its tests, readme, etc

Is it possible to install a package via npm and exclude its tests and other files not necessary for using it?
Many packages include a lot of unnecessary files, I've seen some of them even include JPEG images for some testing - I don't want to download that, I just want to use their APIs.
You can't, because npm downloads all the files whether it's required or not. However it is possible to import part of the npm library in your app.
If you want you can delete unused part manually from node_modules folder. But I'll not recommend it.

JHipster: Why node_modules and other front-end files got generated for --skip-client flag?

I created a new JHipster project with the following command:
jhipster --skip-client
Since, I skipped client generation via --skip-client, why the newly created project contains the following files and folders which I think are related to frontend and not related to backend anywhere:
node_modules
package.json
.yo-rc.json
yarn.lock
From this link, it seems like it is actually a feature and not a bug.
The purpose of installing a local copy of generator-jhipster is that if you upgrade your global version, the local version will still match what your project uses. This protects you from using a newer entity generator on an older project. You can skip the installation of the local generator-jhipster by using --skip-install (note that your project will then always use the global generator-jhipster)
The .yo-rc.json file has the answers to your prompt and other details about your project that help with the other subgenerators such as entity or import-jdl. This file is important to keep.

Resources