Uploaded image for project: 'James Server'
  1. James Server
  2. JAMES-3190

System architecture is not apparent in the code

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • Documentation
    • None

    Description

      I have added this issue as "Documentation" for now.

      I was told that James has a hexogonal architecture. However, that is not at all apparent neither in the documentation, nor in the code itself.

      If this is truly the fundamental concept of the system design, then for developers to understand the system more easily it ought to be made more explicit in the code, in one way or another (or in as many ways as reasonably possible).

      Attachments

        Issue Links

        is part of

        Improvement - An improvement or enhancement to an existing feature or task. JAMES-3258 Update Documentation for version <3.5.0

        • Major - Major loss of function.
        • Open
        relates to

        Improvement - An improvement or enhancement to an existing feature or task. JAMES-3187 Update James Documentation

        • Major - Major loss of function.
        • Open

        Task - A task that needs to be done. JAMES-3193 Update Developer Guide

        • Major - Major loss of function.
        • Open

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            dleangen David Leangen
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:

              Slack

                Issue deployment