jhipster / generator-jhipster

JHipster is a development platform to quickly generate, develop, & deploy modern web applications & microservice architectures.
https://www.jhipster.tech
Apache License 2.0
21.53k stars 4.02k forks source link

Remove Entity Not working #12320

Closed dkarthi1973 closed 7 months ago

dkarthi1973 commented 4 years ago

jhipster remove-entity entity1 - command is not working while remove entity ( error message remove-entity,entity1 is not a known command. See 'jhipster --help'. could you please advice us to remove the entity from project.

murdos commented 4 years ago

There's no such command. See the related discussion on https://github.com/jhipster/generator-jhipster/issues/8933

mshima commented 4 years ago

@murdos I think this should be relatively easy and non intrusive. We can implement jhipster entity Foo --remove instead of jhipster remove-entity Foo. It should:

CC @jhipster/developers

pascalgrimaud commented 4 years ago

It could be done but I'm not sure it is usefull.

Personally, in my real project, once an entity is already generated, if I want to remove it, I'd prefer to do it manually, rather than depending on JHipster. It would take only few minutes to do that.

So not sure, it deserves a new flag in our entity sub gen, which is already complex.

deepu105 commented 4 years ago

Agree with Pascal. We have had this discussion many times. Removing entity manually using an IDE is much more easier then coding it for the generator. Once you start customizing stuff you can't use the generator to remove those anyway and that will be the more realistic case. So we will be maintaining the option for no much value. To me its just overhead

On Thu, 27 Aug 2020, 11:13 pm Pascal Grimaud, notifications@github.com wrote:

It could be done but I'm not sure it is usefull.

Personally, in my real project, once an entity is already generated, if I want to remove it, I'd prefer to do it manually, rather than depending on JHipster. It would take only few minutes to do that.

So not sure, it deserves a new flag in our entity sub gen, which is already complex.

— You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub https://github.com/jhipster/generator-jhipster/issues/12320#issuecomment-682193835, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIOKF763KXTDKM5ICCOC4LSC3D6NANCNFSM4QMZDRYA .

Tcharl commented 7 months ago

What about the technical data (the relationships to this entity in .jhipster/.json and the .jhipster/.json? At least, it has to be explained in the tips and tricks: our users should know how to do that if they are using side-side and regular regens

github-actions[bot] commented 7 months ago

JHipster has completed the sample check .yo-rc.json: Entities JDL: Application: successfully generated Frontend check: skipped Backend check: skipped E2E check: skipped

This check uses jhipster info output from the issue description to generate the sample. Bug report that does not contain this information will be marked as invalid.