What's a good practice to deal with global strings in angular?












1















In our angular application we have a few hardcoded strings across the app (things like labels, error messages, validation messages) and would like to organize that mess a bit. I read a few answers on stackoverflow about global strings but I couldn't understand if this is a bad practice or not (for example here they say it's a bad thing).



To me it feels like a regular problem to have, so what are the good practices to deal with global variables in Angular?










share|improve this question























  • read this article medium.com/beautiful-angular/…

    – Artyom Amiryan
    Nov 21 '18 at 11:53











  • a part of the environment files we have some files like app.const.ts and we export constants. Like this: export const col_type = {}

    – manelseo
    Nov 21 '18 at 11:55













  • Honestly, to each his own preference. But global variables are indeed bad, we can all agree on that. My preferred way is Injection Tokens and factories, as you can inject the strings directly as dependencies of your components.

    – trichetriche
    Nov 21 '18 at 11:55











  • If the strings change when you change an environment (for instance URLs), you can use the environment files to manage them.

    – trichetriche
    Nov 21 '18 at 11:56
















1















In our angular application we have a few hardcoded strings across the app (things like labels, error messages, validation messages) and would like to organize that mess a bit. I read a few answers on stackoverflow about global strings but I couldn't understand if this is a bad practice or not (for example here they say it's a bad thing).



To me it feels like a regular problem to have, so what are the good practices to deal with global variables in Angular?










share|improve this question























  • read this article medium.com/beautiful-angular/…

    – Artyom Amiryan
    Nov 21 '18 at 11:53











  • a part of the environment files we have some files like app.const.ts and we export constants. Like this: export const col_type = {}

    – manelseo
    Nov 21 '18 at 11:55













  • Honestly, to each his own preference. But global variables are indeed bad, we can all agree on that. My preferred way is Injection Tokens and factories, as you can inject the strings directly as dependencies of your components.

    – trichetriche
    Nov 21 '18 at 11:55











  • If the strings change when you change an environment (for instance URLs), you can use the environment files to manage them.

    – trichetriche
    Nov 21 '18 at 11:56














1












1








1








In our angular application we have a few hardcoded strings across the app (things like labels, error messages, validation messages) and would like to organize that mess a bit. I read a few answers on stackoverflow about global strings but I couldn't understand if this is a bad practice or not (for example here they say it's a bad thing).



To me it feels like a regular problem to have, so what are the good practices to deal with global variables in Angular?










share|improve this question














In our angular application we have a few hardcoded strings across the app (things like labels, error messages, validation messages) and would like to organize that mess a bit. I read a few answers on stackoverflow about global strings but I couldn't understand if this is a bad practice or not (for example here they say it's a bad thing).



To me it feels like a regular problem to have, so what are the good practices to deal with global variables in Angular?







angular






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 21 '18 at 11:51









Alex LunguAlex Lungu

4611616




4611616













  • read this article medium.com/beautiful-angular/…

    – Artyom Amiryan
    Nov 21 '18 at 11:53











  • a part of the environment files we have some files like app.const.ts and we export constants. Like this: export const col_type = {}

    – manelseo
    Nov 21 '18 at 11:55













  • Honestly, to each his own preference. But global variables are indeed bad, we can all agree on that. My preferred way is Injection Tokens and factories, as you can inject the strings directly as dependencies of your components.

    – trichetriche
    Nov 21 '18 at 11:55











  • If the strings change when you change an environment (for instance URLs), you can use the environment files to manage them.

    – trichetriche
    Nov 21 '18 at 11:56



















  • read this article medium.com/beautiful-angular/…

    – Artyom Amiryan
    Nov 21 '18 at 11:53











  • a part of the environment files we have some files like app.const.ts and we export constants. Like this: export const col_type = {}

    – manelseo
    Nov 21 '18 at 11:55













  • Honestly, to each his own preference. But global variables are indeed bad, we can all agree on that. My preferred way is Injection Tokens and factories, as you can inject the strings directly as dependencies of your components.

    – trichetriche
    Nov 21 '18 at 11:55











  • If the strings change when you change an environment (for instance URLs), you can use the environment files to manage them.

    – trichetriche
    Nov 21 '18 at 11:56

















read this article medium.com/beautiful-angular/…

– Artyom Amiryan
Nov 21 '18 at 11:53





read this article medium.com/beautiful-angular/…

– Artyom Amiryan
Nov 21 '18 at 11:53













a part of the environment files we have some files like app.const.ts and we export constants. Like this: export const col_type = {}

– manelseo
Nov 21 '18 at 11:55







a part of the environment files we have some files like app.const.ts and we export constants. Like this: export const col_type = {}

– manelseo
Nov 21 '18 at 11:55















Honestly, to each his own preference. But global variables are indeed bad, we can all agree on that. My preferred way is Injection Tokens and factories, as you can inject the strings directly as dependencies of your components.

– trichetriche
Nov 21 '18 at 11:55





Honestly, to each his own preference. But global variables are indeed bad, we can all agree on that. My preferred way is Injection Tokens and factories, as you can inject the strings directly as dependencies of your components.

– trichetriche
Nov 21 '18 at 11:55













If the strings change when you change an environment (for instance URLs), you can use the environment files to manage them.

– trichetriche
Nov 21 '18 at 11:56





If the strings change when you change an environment (for instance URLs), you can use the environment files to manage them.

– trichetriche
Nov 21 '18 at 11:56












1 Answer
1






active

oldest

votes


















0














You can externalize all of this in json configuration files, loaded at launch. It allows to reuse them multiple time. Moreover, you can define multiple configurations for multiple environments.
Take a look at this article : https://blogs.msdn.microsoft.com/premier_developer/2018/03/01/angular-how-to-editable-config-files/






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%2f53411451%2fwhats-a-good-practice-to-deal-with-global-strings-in-angular%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    You can externalize all of this in json configuration files, loaded at launch. It allows to reuse them multiple time. Moreover, you can define multiple configurations for multiple environments.
    Take a look at this article : https://blogs.msdn.microsoft.com/premier_developer/2018/03/01/angular-how-to-editable-config-files/






    share|improve this answer




























      0














      You can externalize all of this in json configuration files, loaded at launch. It allows to reuse them multiple time. Moreover, you can define multiple configurations for multiple environments.
      Take a look at this article : https://blogs.msdn.microsoft.com/premier_developer/2018/03/01/angular-how-to-editable-config-files/






      share|improve this answer


























        0












        0








        0







        You can externalize all of this in json configuration files, loaded at launch. It allows to reuse them multiple time. Moreover, you can define multiple configurations for multiple environments.
        Take a look at this article : https://blogs.msdn.microsoft.com/premier_developer/2018/03/01/angular-how-to-editable-config-files/






        share|improve this answer













        You can externalize all of this in json configuration files, loaded at launch. It allows to reuse them multiple time. Moreover, you can define multiple configurations for multiple environments.
        Take a look at this article : https://blogs.msdn.microsoft.com/premier_developer/2018/03/01/angular-how-to-editable-config-files/







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 21 '18 at 12:03









        vebenveben

        2,16041329




        2,16041329
































            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%2f53411451%2fwhats-a-good-practice-to-deal-with-global-strings-in-angular%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







            這個網誌中的熱門文章

            Xamarin.form Move up view when keyboard appear

            Post-Redirect-Get with Spring WebFlux and Thymeleaf

            Anylogic : not able to use stopDelay()