Dropdown with inline JS issue in 3.9.4

Description

After upgrading to v3.9.4, I faced a major problem with my dropdown.

Steps to Reproduce

1. Update to v3.9.4
2. Create a Dropdown looking like this one : (You can obviously use any bool condition instead of hasRole)

<Dropdown
  id="security-dropdown"
  trigger={
    <a href="#!">
      Sécurité <Icon right>arrow_drop_down</Icon>
    </a>
  }>
  {hasRole('ROLE_GUARDIAN') ? (
    <>
      <Link to={`/${userType}/email`}>Adresse Mail</Link>
      <Link to={`/${userType}/other`}>Autre</Link>
    </>
  ) : (
    <Link to={`/${userType}/password`}>Mot de Passe</Link>
  )}
</Dropdown>

1. Admire this beautiful error : TypeError: (intermediate value).filter is not a function located at renderItems xxxxx/node_modules/react-materialize/lib/Dropdown.js:54

Expected behavior: Display correctly the dropdown as it was working in v3.9.3

Actual behavior: The temporary fix that I found is to make to separate conditions.

<Dropdown
  id="security-dropdown"
  trigger={
    <a href="#!">
      Sécurité <Icon right>arrow_drop_down</Icon>
    </a>
  }>
  {hasRole('ROLE_GUARDIAN') && (
    <Link to={`/${userType}/email`}>Adresse Mail</Link>
  )}
  {hasRole('ROLE_GUARDIAN') && (
    <Link to={`/${userType}/other`}>Autre</Link>
  )}
  {!hasRole('ROLE_GUARDIAN') && (
    <Link to={`/${userType}/password`}>Mot de Passe</Link>
  )}
</Dropdown>

Explanations : The PR #1164 made by @MauAbata changed the way Dropdowns are rendered, that had impact on my code, and I suppose and many others.

Versions

react-materialize: 3.9.4 materialize-css: 1.0.0 react: 17.0.1

[alextrastero]

Should be fixed in 3.9.5

[MauAbata]

@alextrastero I just realized that the current code will most likely break on any single-element Dropdown, which includes simple things like

<Dropdown>
  <a>I'm an only child</a>
</Dropdown>

Since the components prop in that case is just the one child, not an array. I’ve created a PR to fix this and recurse into Fragments: https://github.com/react-materialize/react-materialize/pull/1168

@Tchekda Out of curiosity, and if it is easily possible for you to build from the branch, can you try my current PR with your original code using the fragments?