Does it make sense to create a js class in a reactJS project?












1















I would like to have your opinion on the following.



Does it make sense to create and use a « pure » javascript class inside of a reactJS project ?
I mean for exemple I want to create let say a character class in a game (with methods affecting his state, health etc…). But I don’t especially want to have a visual component showing my character. I could separate all methods with different buttons etc, but then all my methods would be in different places.



Im basically wondering if it makes sense to think that way with a reactJS project or if I should just rethink the whole thing in a more « react » way?










share|improve this question























  • What you're describing means that a state is stored as class instance. It generally doesn't make sense because React encourages functional approach and plain objects for state. Using classes without knowing all consequences may result in awkward situations regarding app design in future. This also won't play well with Redux if you're serious about state management.

    – estus
    Nov 13 '18 at 11:21













  • @estus yes i see what you mean. Indeed if i create a class it's going to be tricky (or not really clean?) to link my class and my state (I am using redux). So i should maybe think about making my reducer in a way that he will have the methods that my class would have had. Would it make more sense ?

    – asecret
    Nov 13 '18 at 11:22











  • If you're already using Redux then I guess there's nothing to think about, it promotes immutability, this doesn't work well with OOP. Yes, class methods will be transformed to separate functions in this case - reducers or else.

    – estus
    Nov 13 '18 at 11:28
















1















I would like to have your opinion on the following.



Does it make sense to create and use a « pure » javascript class inside of a reactJS project ?
I mean for exemple I want to create let say a character class in a game (with methods affecting his state, health etc…). But I don’t especially want to have a visual component showing my character. I could separate all methods with different buttons etc, but then all my methods would be in different places.



Im basically wondering if it makes sense to think that way with a reactJS project or if I should just rethink the whole thing in a more « react » way?










share|improve this question























  • What you're describing means that a state is stored as class instance. It generally doesn't make sense because React encourages functional approach and plain objects for state. Using classes without knowing all consequences may result in awkward situations regarding app design in future. This also won't play well with Redux if you're serious about state management.

    – estus
    Nov 13 '18 at 11:21













  • @estus yes i see what you mean. Indeed if i create a class it's going to be tricky (or not really clean?) to link my class and my state (I am using redux). So i should maybe think about making my reducer in a way that he will have the methods that my class would have had. Would it make more sense ?

    – asecret
    Nov 13 '18 at 11:22











  • If you're already using Redux then I guess there's nothing to think about, it promotes immutability, this doesn't work well with OOP. Yes, class methods will be transformed to separate functions in this case - reducers or else.

    – estus
    Nov 13 '18 at 11:28














1












1








1








I would like to have your opinion on the following.



Does it make sense to create and use a « pure » javascript class inside of a reactJS project ?
I mean for exemple I want to create let say a character class in a game (with methods affecting his state, health etc…). But I don’t especially want to have a visual component showing my character. I could separate all methods with different buttons etc, but then all my methods would be in different places.



Im basically wondering if it makes sense to think that way with a reactJS project or if I should just rethink the whole thing in a more « react » way?










share|improve this question














I would like to have your opinion on the following.



Does it make sense to create and use a « pure » javascript class inside of a reactJS project ?
I mean for exemple I want to create let say a character class in a game (with methods affecting his state, health etc…). But I don’t especially want to have a visual component showing my character. I could separate all methods with different buttons etc, but then all my methods would be in different places.



Im basically wondering if it makes sense to think that way with a reactJS project or if I should just rethink the whole thing in a more « react » way?







javascript reactjs class






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 13 '18 at 11:09









asecretasecret

62




62













  • What you're describing means that a state is stored as class instance. It generally doesn't make sense because React encourages functional approach and plain objects for state. Using classes without knowing all consequences may result in awkward situations regarding app design in future. This also won't play well with Redux if you're serious about state management.

    – estus
    Nov 13 '18 at 11:21













  • @estus yes i see what you mean. Indeed if i create a class it's going to be tricky (or not really clean?) to link my class and my state (I am using redux). So i should maybe think about making my reducer in a way that he will have the methods that my class would have had. Would it make more sense ?

    – asecret
    Nov 13 '18 at 11:22











  • If you're already using Redux then I guess there's nothing to think about, it promotes immutability, this doesn't work well with OOP. Yes, class methods will be transformed to separate functions in this case - reducers or else.

    – estus
    Nov 13 '18 at 11:28



















  • What you're describing means that a state is stored as class instance. It generally doesn't make sense because React encourages functional approach and plain objects for state. Using classes without knowing all consequences may result in awkward situations regarding app design in future. This also won't play well with Redux if you're serious about state management.

    – estus
    Nov 13 '18 at 11:21













  • @estus yes i see what you mean. Indeed if i create a class it's going to be tricky (or not really clean?) to link my class and my state (I am using redux). So i should maybe think about making my reducer in a way that he will have the methods that my class would have had. Would it make more sense ?

    – asecret
    Nov 13 '18 at 11:22











  • If you're already using Redux then I guess there's nothing to think about, it promotes immutability, this doesn't work well with OOP. Yes, class methods will be transformed to separate functions in this case - reducers or else.

    – estus
    Nov 13 '18 at 11:28

















What you're describing means that a state is stored as class instance. It generally doesn't make sense because React encourages functional approach and plain objects for state. Using classes without knowing all consequences may result in awkward situations regarding app design in future. This also won't play well with Redux if you're serious about state management.

– estus
Nov 13 '18 at 11:21







What you're describing means that a state is stored as class instance. It generally doesn't make sense because React encourages functional approach and plain objects for state. Using classes without knowing all consequences may result in awkward situations regarding app design in future. This also won't play well with Redux if you're serious about state management.

– estus
Nov 13 '18 at 11:21















@estus yes i see what you mean. Indeed if i create a class it's going to be tricky (or not really clean?) to link my class and my state (I am using redux). So i should maybe think about making my reducer in a way that he will have the methods that my class would have had. Would it make more sense ?

– asecret
Nov 13 '18 at 11:22





@estus yes i see what you mean. Indeed if i create a class it's going to be tricky (or not really clean?) to link my class and my state (I am using redux). So i should maybe think about making my reducer in a way that he will have the methods that my class would have had. Would it make more sense ?

– asecret
Nov 13 '18 at 11:22













If you're already using Redux then I guess there's nothing to think about, it promotes immutability, this doesn't work well with OOP. Yes, class methods will be transformed to separate functions in this case - reducers or else.

– estus
Nov 13 '18 at 11:28





If you're already using Redux then I guess there's nothing to think about, it promotes immutability, this doesn't work well with OOP. Yes, class methods will be transformed to separate functions in this case - reducers or else.

– estus
Nov 13 '18 at 11:28












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%2f53279703%2fdoes-it-make-sense-to-create-a-js-class-in-a-reactjs-project%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%2f53279703%2fdoes-it-make-sense-to-create-a-js-class-in-a-reactjs-project%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

Florida Star v. B. J. F.

Danny Elfman

Lugert, Oklahoma