“It hasn’t suggested that a fictitious method change will fix the issue.” Paul’s point about the duck is also the duck’s point about Nova. An assistant can invent an API that looks right, name it well, and call it in a fix that compiles in its head and nowhere else.
Three checks before you accept a fix
- Does it exist? Search the codebase and the library’s docs for the function, option or flag. Not the assistant’s memory. The real thing.
- Does it do that? Read the signature. Hallucinated methods often borrow a real name with an imaginary parameter.
- Does it fit the version? The method may be real in version 5 and gone in version 7, which is the one you run.
grep -rn "methodName" src/ vendor/ # is it anywhere in the project?
php -r 'var_dump( method_exists( "ClassName", "methodName" ) );'Prompt to steal
For every function, method, option or flag in your fix, give me the file
and line where it is defined in this project or the vendor directory, or a
link to the official docs for the version we use. If you can't, say
"unverified" next to it. Don't remove unverified items; mark them.An assistant that has to show the definition finds out it doesn’t exist before you do.
