The following demos either missing (even tho they have sections in the demo page):

• CircularProgress
• DraggableCard
• Scrollable

Demos are not working for most of the components.So it is harder to debug

See issue on verse change when current page selected is greater than number of pages on new verse. probably should change current page to 1st whenever verse changes

TWL files have a list of words for a given bible reference linking to the markdown files

Modal displayed when the 3 dot menu is clicked.

https://projects.invisionapp.com/share/6VZ7U05QCMN#/screens/435786049

https://projects.invisionapp.com/share/6VZ7U05QCMN#/screens/435786052

Switch to use MUI TextareaAutosize instead

DoD:

This error doesn't occur while running styleguidest

Details:

The following error occurs when running the test application:

$ yarn start
yarn run v1.22.19
$ styleguidist server
ℹ ｢wds｣: Project is running at http://localhost:6060/
ℹ ｢wds｣: webpack output is served from undefined
ℹ ｢wds｣: Content not from webpack is served from /Users/noah/src/translation-helps-rcl
You can now view your style guide in the browser:

  Local:            http://localhost:6060/
  On your network:  http://172.16.103.170:6060/

Error: error:0308010C:digital envelope routines::unsupported
Error: error:0308010C:digital envelope routines::unsupported

From what I gather this is a compatibility issue between Node16 and Node18.

Current solutions involve either:

1. a global environment downgrade to Node16
2. Using tools like nvm
3. run the application using NODE_OPTIONS=--openssl-legacy-provider yarn start if they are running Node18.

Essentially this bring us to the question: Here are a few things to consider:

1. Should we begin upgrading this lib to support Node18
2. Should we begin enforcing Node versions in the package.json?
3. Do we still need Node16 support in this library? (3) above works for me and I do not notice any broken functionality once the styleguidest app builds and runs. I'm not sure what affect running higher versions of node will have on other machines though.
4. How wide-spread is this library and how many of those dependents use Node16? That is, what would the "damage report" be if we did an upgrade?

Personally I would recommend upgrading to at least Node18 as sticking to latest LTS versions are typically a good idea.

If we decide to stick with Node16 for now I would recommend we use the engines config in package.json to ensure global compatibility of this library across other apps. New developers (especially those new to JS development) would most likely have the latest version of the LTS Node installed and will run into this issue. There is no mention of using Node16 in the README, however it would be much better to enforce this technically (rather than relying on developers to parse a README file).

This same issue appears in other apps (such as gateway-edit) and could benefit from an upgrade away from Node16 as well.

currently if the property closeable is true, then a tool bar cannot be used. Code in Card.js:

        {closeable ? (
          <CloseIcon
            id='settings_card_close'
            className={classes.pointerIcon}
            onClick={onClose}
          />
        ) : (
          <FlexDiv>
            <Extensible onRenderItems={onRenderToolbar}>
              {alert && (
                <IconButton
                  aria-label='warning'
                  onClick={onAlertClick}
                  className={classes.margin}
                  key='alert-button'
                >
... elided ...
            {!disableSettingsButton && (
              <MoreVertIcon
                id={cardMenuId}
                className={classes.pointerIcon}
                onClick={onMenuClick}
              />
            )}
          </FlexDiv>

We ( Autographa ) are facing an issue on loading contents ( Tn, Tq, Ta etc. ) using the helps-rcl. The issue arise when the react version updated to 18. This issue is only happening when the contents load using rcl and not for the pre fetched (offline) contents displayed using the rcl. Hope the video in the link gives more clarity on the issue. Helps-rcl-issue-react-18

The following functions need DOOR43_CATALOG constant to be abstracted.

Process:

see unfoldingWord/gateway-edit#460

newVarName = "door43Catalog"

main = do
  sequence refactorDoor43Catalog ["loadGlBible", "getGlAlignmentBiblesList"]
  removeConstant DOOR43_CATALOG
  sequence abstract allRepositoriesUsingTranslationHelps

refactorDoor43Catalog =
  def
  >> replaceName "DOOR43_CATALOG" newVarName
  >> abstract

abstract = id >|< abstractLocalFunc

abstractLocalFunc = 
  prependVarNameToFuncDef newVarName
  >> callsites 
  >> sequence (applyVar newVarName >> abstract)

• tsv performance (render ,caching, parsing)