Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Config writing gruidelines

Open
#21 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
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
php
Domain
documentation

Research direction

No file, test, or entry point is named. Start by locating the project's INI or configuration documentation and confirm the intended scope with maintainers; done means an agreed, concise guideline covering component-owned configuration, defaults, and namespaced variables.

Written by the indexing model from the issue text.

Description

discussion

We should keep a nice and small subset of guidelines on wrtting INI files, mainly to be used as a requirement to make a INI a Respected, thought something like this:

  • Configuration for a specific ini should be handled by it, the more, the better. Stick with the defaults mentioned by the component, if none we fall back to PHP standards
  • Configuration variables (not instance objects) on a ini should have a namespace reflecting the INI filename to prevent conflitcs with other Respecteds
Dominant language
PHP
Stars
99
Forks
7
No merged PRs in 30d

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 Respect/Config

All issues in Respect/Config

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.