I have a ParentModule.update function, which in turn calls ChildModule.update function. Nothing weird, very basic, very normal The Elm Architecture stuff. Should ChildModule expose the constructors for its Msg type? Should the ParentModule.update function be able to inspect the child’s messages? …

[image] xarvh: Should ChildModule expose the constructors for its Msg type? Should the ParentModule.update function be able to inspect the child’s messages? Should the Msg constructors be considered part of the interface, or should the type be opaque? Does anyone have actual experience with a…

I think I have been unclear. I don’t have a problem with one particular module, I’m trying to figure out a general rule to manage very large projects (100K+ LOC) that will likely share a lot of code but use it differently. To this extent, reusability is very important and putting everything in a s…

[image] xarvh: I don’t have a problem with one particular module, I’m trying to figure out a general rule to manage very large projects (100K+ LOC) that will likely share a lot of code but use it differently. To this extent, reusability is very important and putting everything in a single modul…

Hi @xarvh ! For me it makes a lot of sense to replicate TEA on child modules, each of them with it’s own Msg, Model, update, and view. I tend to keep the state of this components transient, when the user visits a certain route this component gets initialized possibly using URL params. In this way th…

Are you refactoring an existing 100K LOC project? Or starting work on a new project that may grow that large? I did the first, and am starting the second. I have very little formal training or experience with OO programming. Are you sure about that? Yes. I am. Be smart, and don’t go down …

Thank you. I am familiar with a couple of different incarnations of OutMsg, and my usual approach is something like that. However I am working with a codebase that uses the child Msg as a way to communicate with the parent, and while I don’t see any horrible downside, I feel like it doesn’t define…

[image] xarvh: Wouldn’t that require the child to know what OuterMsgs are? Exactly, OuterMsg defines an the interface that the children are to use to communicate with the parent, and outerMsg function maps the child message to something the parent knows how to deal with. In my case these chi…

[image] xarvh: Be smart, and don’t go down this route - but I think you sort of have to to learn from the mistake This is not very charitable of you; our solutions have been working well, in production, for a few years now. Apologies if my response did not come accross well, I certainly di…

[image] xarvh: I am familiar with a couple of different incarnations of OutMsg, and my usual approach is something like that. However I am working with a codebase that uses the child Msg as a way to communicate with the parent, and while I don’t see any horrible downside, I feel like it doesn’t…

[image] rupert: Apologies if my response did not come accross well, I certainly did not intend to imply that you are not smart. No worries. If you allow me a small nitpick, it’s not a matter of smarts (I don’t think I’m particularly smart), it is a matter of not dismissing someone else’s exp…

Should a module expose its Msg constructors?

Learn

Topic		Replies	Views
Commands and messages from/to child models Learn	9	3293	August 23, 2021
Modifying "parent state" from child page in an elm-spa-example-like architecture Learn	19	6711	November 25, 2018
Question about good taco technique for Elm SPAs Request Feedback	17	3148	July 31, 2018
New view API design technique and accompanying blog post Request Feedback	22	4188	March 11, 2018
Is TEA a comonad? Learn	18	3529	January 16, 2018

Should a module expose its Msg constructors?

Related topics