Skip to content

Suggestion on modules: When you get to them consider also the TidyModule approach #22

Open
@D3SL

Description

@D3SL

Having read the first two parts of Reactivity Tips and Tricks I think you may like the TidyModule approach to modules more than stock. They use R6 class objects to hold both the UI and Server functions of a module as well and created a built in port system for piping data in and out of their modules.

If you're making apps with lots of repeated complicated code blocks it's imho a much better approach than stock modules, although if a majority of your app consists of individual bespoke pieces I'd just as soon skip the OO approach entirely. Sometimes all you want is a banana and not a gorilla troop factory to produce a stateful gorilla to hold the banana. Since we spend easily several times as much time reading code as writing it I'm a fan of balancing clever parsimony against clear legibility.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions