Removing Unused PropTypes in Volto Training Documentation - Best Practices?

Hello Everyone,

I am currently going through the Volto training documentation and I have come across a component named Header.jsx [LINK] . In this component, I noticed that there are PropTypes defined for token and content which are not being used anywhere in the component.

original code:

import { Container, Segment } from 'semantic-ui-react';
import PropTypes from 'prop-types';

import { Logo, Navigation, Icon } from '@plone/volto/components';
import zoomSVG from '@plone/volto/icons/zoom.svg';

const Header = ({ pathname }) => {
  return (
    <Segment basic className="header-wrapper" role="banner">
        <div className="header">
          <div className="logo-nav-wrapper">
            <div className="logo">
              <Logo />
          <div className="nav-wrapper">
            <Navigation pathname={pathname} />
          <div className="tools-search-wrapper">
            <a className="try-now-link" href="">
              Try now
            <div className="search">
              <button className="search-button" aria-label="search">
                <Icon name={zoomSVG} size="18px" />
              </button>{' '}

export default Header;

Header.propTypes = {
  token: PropTypes.string,
  pathname: PropTypes.string.isRequired,
  content: PropTypes.objectOf(PropTypes.any),

Header.defaultProps = {
  token: null,
  content: null,

replace with


Header.propTypes = {
  pathname: PropTypes.string.isRequired,

Header.defaultProps = {};

While I understand that PropTypes are a great way to validate the props for a component, these unused PropTypes are causing unnecessary clutter in the code. They can potentially lead to confusion for developers who are new to Volto and are trying to understand the codebase.

I believe that removing these unused PropTypes could improve the readability and maintainability of the code, especially for those who are new to Volto. It would make the code cleaner and easier to understand, thus making the learning process smoother.

However, I wanted to get your thoughts on this. Is there any reason these PropTypes are included in the training documentation? Is there a better way to handle this situation?