Feature Request: Move Lectern JS Client into monorepo

[joneubank]

We want to move the lectern client codebase into this repository so they can be maintained as part of the same monorepo.

Current js-lectern-client repo: https://github.com/overture-stack/js-lectern-client

There are many advantages to this move, but some important ones are:

• using the same type system between server and client
• enforcing changes to dictionary model are reflected in server and validation engine at same time
• simplifying documentation and user onboarding by gathering information about server and client in the same location

Details

• [x] Create a new monorepo directory called packages to store packages published to npm
• [x] Create a new package called client to store the js-lectern-client code
• [x] Move existing lectern client code here

Once the client code is co-located with the server additional issues will be needed to track some improvements to the client from its current state

• [x] Update the types used by the client to reference the dictionary library
• [x] Move data validation into a shared library so it is usable on the server or in the client
• [x] Remove the generated HTML dev docs and standardize documentation between server and client
• [x] README documentation for devs, client functionality and how to use

Once the client has been published from this repository:

• [ ] #214

[joneubank]

Removed the task to make the client runnable in browser and moved that to its own issue: #213 . The changes to allow this relate to script validations and it is desired to remove these instead of modifying that code at all. Temporarily we will live with this non browser version.

[joneubank]

Readme updated to describe current state: https://github.com/overture-stack/lectern/commit/6784f6c74812ac3f7627ac53d06679088e57f0bf

[joneubank]

Closing this ticket with the client merged and available in current state. Future work is needed to make it usable in the browser.

Other tasks that should be considered:

• Export all lectern dictionary content in the client, writing lectern types and parsing dictionaries is behaviour I would want from the client.
• Expose validation functions, currently only processing is available
• Rename the processing functions
• Separate processing into:
  • data structure validation
  • data type conversion
  • data value validation