New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

No support for components that directly return `null` #926

Open

rvetere opened this issue May 30, 2024 · 0 comments · May be fixed by #924

Contributor

rvetere commented May 30, 2024

If a component directly returns null like this:

export const DataTableColumnDocs: FunctionComponent<
  IDataTableColumn<object>
> = () => {
  return null;
};

Then it won't find any interface to parse. The same behavior can be seen when a component directly returns a prop like so:

export const AuthenticatedBoundary = ({
  children,
  fallback,
}: AuthenticatedBoundaryProps) => {
  const { isLoggedIn } = useAuthentication();

  if (!isLoggedIn) {
    return fallback;
  }

  return children;
};

rvetere linked a pull request

that will close this issue

Add support for function components that return null #924

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment