Create a hook for validating file name

Open
#147 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python

Research direction

No implementation files, tests, or entry points are named. Review the existing hooks in ansys/pre-commit-hooks first, then clarify the target documentation paths, exact lowercase-and-hyphen convention, configuration needs, and validation coverage; done means noncompliant documentation filenames are reliably detected.

Written by the indexing model from the issue text.

Description

💡 Idea

When it comes to documentation, the usage of lowercase and hyphens in files names is important. This is because the name of the files set the final slug in the URL of the docs.

It is likely that a developer uses snake case or camel case when creating a source code file. However, these naming conventions should be avoided for files that render into docs.

Thus, I am proposing the creation of a hook that ensures a file is compliant with a certain naming convention.

Dominant language
Python
Stars
5
Forks
1
Avg merge
1h 47m
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ansys/pre-commit-hooks

All issues in ansys/pre-commit-hooks

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.