Skip to content

Library Structure #17

@mj-meyer

Description

@mj-meyer

This is how I envision the library structure should look like roughly. Only highlighted the most important points. Most interfaces and presentational components aren't listed. This is only to help me stay sane and make sure I create the right libraries.

Anything in BOLD is a library on its own.

interfaces

  • joke interface

feature-joke

  • data-access-joke
    • api call to joke
  • container
    • INIT load from localstorage (feature-joke-state)
    • ADD/Remove to/from favourites (feature-joke-state)
      • Is joke in favourites? (feature-joke-state - exists)
      • add one
      • remove one
    • NEW joke
    • SHARE joke (feature-share)

feature-joke-state (localStorage)

  • add one
  • delete one
  • exists - get one by id
  • get all
  • delete all

feature-favourites

  • container
    • INIT open modal
    • INIT load list (feature-share - data-access-share - get)
    • share list (feature-share - post)
    • delete list (feature-joke-state - delete all)
    • delete one (feature-joke-state - delete one)
    • close modal

feature-share

  • data-access-share
    • post api call to MYJSON
    • get api call to MYJSON
  • container
    • INIT open modal
    • share joke/s (data-access-share - post)
    • copy link to clipboard

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentation

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions