Skip to content
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.

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

Add "meaninglessFileNames" option #304

Merged

Commits on Nov 25, 2021

  1. Add "meaninglessFileNames" option

    The "meaninglessFileNames" option provides the user with more precise
    control over the component display name.
    
    This option is to be used in conjunction with "displayName" and
    "fileName". If either is set to false, this option will have no effect.
    
    Prior to this commit, when both "displayName" and "fileName" were set,
    the behaviour was to prepend the file name to the component display name
    if it was named anything other than "index", and to prepend the
    directory name otherwise.
    
    The "meaninglessFileNames" option enables developers to control when
    exactly the directory name should be used instead of the file name. If
    the file name is considered to be "meaningless", that is, it doesn't
    provide the developer with any useful information, then the directory
    name will be used instead.
    
    By default, the only "meaningless file name" is "index", which means
    that the default behaviour is unmodified.
    MeLlamoPablo committed Nov 25, 2021
    Copy the full SHA
    b99804c View commit details
    Browse the repository at this point in the history
  2. Add use-directory-name test

    This test case checks whether the "meaninglessFileNames" option is
    applied properly to the "code.js" file and its parent directory name is
    being used instead of its file name.
    MeLlamoPablo committed Nov 25, 2021
    Copy the full SHA
    da023c4 View commit details
    Browse the repository at this point in the history