php / php/doc-en

Enhancement: Explicitly mentioned that the callback must not have any type of error handling

Open
#3,183 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Extension: spl good first issue
Dominant language
XML
Stars
596
Forks
890
Avg merge
1d 15h
Merged PRs (30d)
55

Description

From manual page: https://php.net/function.spl-autoload-register


It seems that I'm not the first one creating a silly sideeffect by adding a error handling into the autoloader when the class can't be loaded.
see e.g. https://stackoverflow.com/questions/15054993/php-autoload-with-exception-handling-waste-of-time

So it is maybe a good enhancement especially for beginners to mention that the callback to register must not raise a throwable if the class could not be loaded because of missing file. Thus would prevent other programmers to repeat this since it is general best pratice to throw an exception if something doesn't is as expected, which would also be the case if the class to autoload does not exist.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start with the SPL autoload register manual page linked in the issue and review the callback requirements around failed class loading. Update the English documentation to clarify that the callback must not raise a throwable when a class cannot be loaded because its file is missing, then verify the page renders correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.