I'm a software developer based in Newcastle Upon Tyne, England. I've got a wide range of experience in companies of varying sizes and cultures, and in roles of varying degrees of responsibility.
Of course, the inverse of that is that the user can in fact change the URL for themselves, so I guess this hasn't actually helped anything at all. D'oh.
GameMsg ToggleInventory, will it, when passed to update, create a new Model that when passed to view will show an inventory? Then imperative makes sense.
If you'd use the name InventoryToggled to denote that the user has e.g. pressed the ToggleInventory button, I'd say you're naming things incorrectly because the inventory wasn't toggled, as the message has not been processed by update yet.
ChangedUrl on the other hand denotes something that definitely did happen. It is more similar to ToggleInventoryButtonPressed.
I'm a software developer based in Newcastle Upon Tyne, England. I've got a wide range of experience in companies of varying sizes and cultures, and in roles of varying degrees of responsibility.
Of course, the inverse of that is that the user can in fact change the URL for themselves, so I guess this hasn't actually helped anything at all. D'oh.
It depends on what those messages are.
GameMsg ToggleInventory, will it, when passed toupdate, create a newModelthat when passed toviewwill show an inventory? Then imperative makes sense.If you'd use the name
InventoryToggledto denote that the user has e.g. pressed theToggleInventorybutton, I'd say you're naming things incorrectly because the inventory wasn't toggled, as the message has not been processed byupdateyet.ChangedUrlon the other hand denotes something that definitely did happen. It is more similar toToggleInventoryButtonPressed.Yeah, the more I think about it the more I think mixed tense (but intentionally so, rather than accidentally so) feels like the way forward here.
Appreciate your input, this has been a useful conversation.
Glad it was of use to you