How can I reduce using extension types in Symfony?





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







-1















In my Controller I am using a lot of extension Types:



use SymfonyComponentFormExtensionCoreTypeTextType;
use SymfonyComponentFormExtensionCoreTypeButtonType;
use SymfonyComponentFormExtensionCoreTypeEmailType;
use SymfonyComponentFormExtensionCoreTypeHiddenType;
use SymfonyComponentFormExtensionCoreTypeRepeatedType;
use SymfonyComponentFormExtensionCoreTypePasswordType;
use SymfonyComponentFormExtensionCoreTypeTextareaType;
use SymfonyComponentFormExtensionCoreTypeSubmitType;


Because this takes so much space and is for me unclear, I need to know if there is one line to use just all lines. Something like this:



use SymfonyComponentFormExtensionCoreTypeAllTypes;









share|improve this question





























    -1















    In my Controller I am using a lot of extension Types:



    use SymfonyComponentFormExtensionCoreTypeTextType;
    use SymfonyComponentFormExtensionCoreTypeButtonType;
    use SymfonyComponentFormExtensionCoreTypeEmailType;
    use SymfonyComponentFormExtensionCoreTypeHiddenType;
    use SymfonyComponentFormExtensionCoreTypeRepeatedType;
    use SymfonyComponentFormExtensionCoreTypePasswordType;
    use SymfonyComponentFormExtensionCoreTypeTextareaType;
    use SymfonyComponentFormExtensionCoreTypeSubmitType;


    Because this takes so much space and is for me unclear, I need to know if there is one line to use just all lines. Something like this:



    use SymfonyComponentFormExtensionCoreTypeAllTypes;









    share|improve this question

























      -1












      -1








      -1








      In my Controller I am using a lot of extension Types:



      use SymfonyComponentFormExtensionCoreTypeTextType;
      use SymfonyComponentFormExtensionCoreTypeButtonType;
      use SymfonyComponentFormExtensionCoreTypeEmailType;
      use SymfonyComponentFormExtensionCoreTypeHiddenType;
      use SymfonyComponentFormExtensionCoreTypeRepeatedType;
      use SymfonyComponentFormExtensionCoreTypePasswordType;
      use SymfonyComponentFormExtensionCoreTypeTextareaType;
      use SymfonyComponentFormExtensionCoreTypeSubmitType;


      Because this takes so much space and is for me unclear, I need to know if there is one line to use just all lines. Something like this:



      use SymfonyComponentFormExtensionCoreTypeAllTypes;









      share|improve this question














      In my Controller I am using a lot of extension Types:



      use SymfonyComponentFormExtensionCoreTypeTextType;
      use SymfonyComponentFormExtensionCoreTypeButtonType;
      use SymfonyComponentFormExtensionCoreTypeEmailType;
      use SymfonyComponentFormExtensionCoreTypeHiddenType;
      use SymfonyComponentFormExtensionCoreTypeRepeatedType;
      use SymfonyComponentFormExtensionCoreTypePasswordType;
      use SymfonyComponentFormExtensionCoreTypeTextareaType;
      use SymfonyComponentFormExtensionCoreTypeSubmitType;


      Because this takes so much space and is for me unclear, I need to know if there is one line to use just all lines. Something like this:



      use SymfonyComponentFormExtensionCoreTypeAllTypes;






      forms symfony controller






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 23 '18 at 16:08









      monkeylovemonkeylove

      2,55011846




      2,55011846
























          2 Answers
          2






          active

          oldest

          votes


















          5














          Each of the classes do something specific, and so using them can't be avoided.



          However, I do like to drop down the namespace, to help make clear what things are (though it's less necessary here, as they are all suffixed). It does reduce a lot of the bulk in the use statements as well. I do find it quite useful where I may have several classes with the same class name, but in different parts of the codebase - maybe an Entity versus some kind of related service.



          <?php
          use SymfonyComponentFormExtensionCoreType;

          ->add('hiddenfieldname', TypeHiddenType::class, [...])
          ->add('password', TypeRepeatedType::class, ....





          share|improve this answer































            2














            I understand your problem. Seeing too much useles code. It's annoying and it makes developoment slower (and less fun :().



            You can use the partial namespace as suggested by @Alister Bulman, but that would disable automatization by coding standard tools (like EasyCodingStandard).



            I want to keep code style automated, so I solve this exact problem by using PHPStorm IDE (it's also free in EAP versions). It nicely collapses the "use" statements:



            enter image description here






            share|improve this answer
























              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%2f53449851%2fhow-can-i-reduce-using-extension-types-in-symfony%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              5














              Each of the classes do something specific, and so using them can't be avoided.



              However, I do like to drop down the namespace, to help make clear what things are (though it's less necessary here, as they are all suffixed). It does reduce a lot of the bulk in the use statements as well. I do find it quite useful where I may have several classes with the same class name, but in different parts of the codebase - maybe an Entity versus some kind of related service.



              <?php
              use SymfonyComponentFormExtensionCoreType;

              ->add('hiddenfieldname', TypeHiddenType::class, [...])
              ->add('password', TypeRepeatedType::class, ....





              share|improve this answer




























                5














                Each of the classes do something specific, and so using them can't be avoided.



                However, I do like to drop down the namespace, to help make clear what things are (though it's less necessary here, as they are all suffixed). It does reduce a lot of the bulk in the use statements as well. I do find it quite useful where I may have several classes with the same class name, but in different parts of the codebase - maybe an Entity versus some kind of related service.



                <?php
                use SymfonyComponentFormExtensionCoreType;

                ->add('hiddenfieldname', TypeHiddenType::class, [...])
                ->add('password', TypeRepeatedType::class, ....





                share|improve this answer


























                  5












                  5








                  5







                  Each of the classes do something specific, and so using them can't be avoided.



                  However, I do like to drop down the namespace, to help make clear what things are (though it's less necessary here, as they are all suffixed). It does reduce a lot of the bulk in the use statements as well. I do find it quite useful where I may have several classes with the same class name, but in different parts of the codebase - maybe an Entity versus some kind of related service.



                  <?php
                  use SymfonyComponentFormExtensionCoreType;

                  ->add('hiddenfieldname', TypeHiddenType::class, [...])
                  ->add('password', TypeRepeatedType::class, ....





                  share|improve this answer













                  Each of the classes do something specific, and so using them can't be avoided.



                  However, I do like to drop down the namespace, to help make clear what things are (though it's less necessary here, as they are all suffixed). It does reduce a lot of the bulk in the use statements as well. I do find it quite useful where I may have several classes with the same class name, but in different parts of the codebase - maybe an Entity versus some kind of related service.



                  <?php
                  use SymfonyComponentFormExtensionCoreType;

                  ->add('hiddenfieldname', TypeHiddenType::class, [...])
                  ->add('password', TypeRepeatedType::class, ....






                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Nov 23 '18 at 16:18









                  Alister BulmanAlister Bulman

                  26.1k656100




                  26.1k656100

























                      2














                      I understand your problem. Seeing too much useles code. It's annoying and it makes developoment slower (and less fun :().



                      You can use the partial namespace as suggested by @Alister Bulman, but that would disable automatization by coding standard tools (like EasyCodingStandard).



                      I want to keep code style automated, so I solve this exact problem by using PHPStorm IDE (it's also free in EAP versions). It nicely collapses the "use" statements:



                      enter image description here






                      share|improve this answer




























                        2














                        I understand your problem. Seeing too much useles code. It's annoying and it makes developoment slower (and less fun :().



                        You can use the partial namespace as suggested by @Alister Bulman, but that would disable automatization by coding standard tools (like EasyCodingStandard).



                        I want to keep code style automated, so I solve this exact problem by using PHPStorm IDE (it's also free in EAP versions). It nicely collapses the "use" statements:



                        enter image description here






                        share|improve this answer


























                          2












                          2








                          2







                          I understand your problem. Seeing too much useles code. It's annoying and it makes developoment slower (and less fun :().



                          You can use the partial namespace as suggested by @Alister Bulman, but that would disable automatization by coding standard tools (like EasyCodingStandard).



                          I want to keep code style automated, so I solve this exact problem by using PHPStorm IDE (it's also free in EAP versions). It nicely collapses the "use" statements:



                          enter image description here






                          share|improve this answer













                          I understand your problem. Seeing too much useles code. It's annoying and it makes developoment slower (and less fun :().



                          You can use the partial namespace as suggested by @Alister Bulman, but that would disable automatization by coding standard tools (like EasyCodingStandard).



                          I want to keep code style automated, so I solve this exact problem by using PHPStorm IDE (it's also free in EAP versions). It nicely collapses the "use" statements:



                          enter image description here







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Nov 24 '18 at 20:05









                          Tomáš VotrubaTomáš Votruba

                          9,83553863




                          9,83553863






























                              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%2f53449851%2fhow-can-i-reduce-using-extension-types-in-symfony%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







                              這個網誌中的熱門文章

                              Academy of Television Arts & Sciences

                              L'Équipe

                              1995 France bombings