Generating new entities in Symfony4 controller












0















I'm trying to generate new entities in a controller in Symfony 4. After generating those, I want to create a database schema based on the entities. But I'm stuck at the first step.



There was this Bundle called SensioGeneratorBundle. This Bundle had the option to generate a entity in the console with using the --no-interaction option and passing a --fields string with the wanted fields and types (here's the guide).



By following this guide, it would've been easy to run the console-command in the controller with the fields and types.



However the SensioGeneratorBundle is now deprecated and not in use for Symfony 4. They replaced it with SymfonyMakerBundle. This cli does have the --no-interaction option, but it doesn't accept the --fields option. When the console-command is started it asks the user interactively to enter the fieldnames and types, which I don't know how to do in the controller. There is this little guide about testing commands with expected input. However this is for testing and I'm not sure if this would be appropriate in a controller.



So I'm stuck at generating entities with no fields.



Does anybody know if there's a workaround? I was thinking of writing a own Maker (guide), but maybe somebody already encountered this problem.










share|improve this question























  • If you know everything that will be going into a new entity, you can just write a file to disk with everything that would be in class that you could write manually.

    – Alister Bulman
    Nov 29 '18 at 12:20
















0















I'm trying to generate new entities in a controller in Symfony 4. After generating those, I want to create a database schema based on the entities. But I'm stuck at the first step.



There was this Bundle called SensioGeneratorBundle. This Bundle had the option to generate a entity in the console with using the --no-interaction option and passing a --fields string with the wanted fields and types (here's the guide).



By following this guide, it would've been easy to run the console-command in the controller with the fields and types.



However the SensioGeneratorBundle is now deprecated and not in use for Symfony 4. They replaced it with SymfonyMakerBundle. This cli does have the --no-interaction option, but it doesn't accept the --fields option. When the console-command is started it asks the user interactively to enter the fieldnames and types, which I don't know how to do in the controller. There is this little guide about testing commands with expected input. However this is for testing and I'm not sure if this would be appropriate in a controller.



So I'm stuck at generating entities with no fields.



Does anybody know if there's a workaround? I was thinking of writing a own Maker (guide), but maybe somebody already encountered this problem.










share|improve this question























  • If you know everything that will be going into a new entity, you can just write a file to disk with everything that would be in class that you could write manually.

    – Alister Bulman
    Nov 29 '18 at 12:20














0












0








0








I'm trying to generate new entities in a controller in Symfony 4. After generating those, I want to create a database schema based on the entities. But I'm stuck at the first step.



There was this Bundle called SensioGeneratorBundle. This Bundle had the option to generate a entity in the console with using the --no-interaction option and passing a --fields string with the wanted fields and types (here's the guide).



By following this guide, it would've been easy to run the console-command in the controller with the fields and types.



However the SensioGeneratorBundle is now deprecated and not in use for Symfony 4. They replaced it with SymfonyMakerBundle. This cli does have the --no-interaction option, but it doesn't accept the --fields option. When the console-command is started it asks the user interactively to enter the fieldnames and types, which I don't know how to do in the controller. There is this little guide about testing commands with expected input. However this is for testing and I'm not sure if this would be appropriate in a controller.



So I'm stuck at generating entities with no fields.



Does anybody know if there's a workaround? I was thinking of writing a own Maker (guide), but maybe somebody already encountered this problem.










share|improve this question














I'm trying to generate new entities in a controller in Symfony 4. After generating those, I want to create a database schema based on the entities. But I'm stuck at the first step.



There was this Bundle called SensioGeneratorBundle. This Bundle had the option to generate a entity in the console with using the --no-interaction option and passing a --fields string with the wanted fields and types (here's the guide).



By following this guide, it would've been easy to run the console-command in the controller with the fields and types.



However the SensioGeneratorBundle is now deprecated and not in use for Symfony 4. They replaced it with SymfonyMakerBundle. This cli does have the --no-interaction option, but it doesn't accept the --fields option. When the console-command is started it asks the user interactively to enter the fieldnames and types, which I don't know how to do in the controller. There is this little guide about testing commands with expected input. However this is for testing and I'm not sure if this would be appropriate in a controller.



So I'm stuck at generating entities with no fields.



Does anybody know if there's a workaround? I was thinking of writing a own Maker (guide), but maybe somebody already encountered this problem.







php symfony symfony4






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 25 '18 at 9:47









ecoeco

7129




7129













  • If you know everything that will be going into a new entity, you can just write a file to disk with everything that would be in class that you could write manually.

    – Alister Bulman
    Nov 29 '18 at 12:20



















  • If you know everything that will be going into a new entity, you can just write a file to disk with everything that would be in class that you could write manually.

    – Alister Bulman
    Nov 29 '18 at 12:20

















If you know everything that will be going into a new entity, you can just write a file to disk with everything that would be in class that you could write manually.

– Alister Bulman
Nov 29 '18 at 12:20





If you know everything that will be going into a new entity, you can just write a file to disk with everything that would be in class that you could write manually.

– Alister Bulman
Nov 29 '18 at 12:20












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53466318%2fgenerating-new-entities-in-symfony4-controller%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53466318%2fgenerating-new-entities-in-symfony4-controller%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Wiesbaden

Marschland

Dieringhausen