silverstripe / silverstripe/developer-docs
why $this->config instead of static::config ?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 7
- Forks
- 74
- Avg merge
- 1d 14m
- Merged PRs (30d)
- 6
Description
Affected Version
4.11
Description
I recently ran Rector on my project and it's complaining about the use of $this->config. Indeed, the method definition is static, so why is it recommended to call $this->config instead of self::config or static::config ?
See docs here: https://docs.silverstripe.org/en/4/developer_guides/configuration/configuration/
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the configuration documentation linked in the issue and locate the guidance that recommends $this->config. Check the surrounding explanation and the reported static method context; done means the documentation clearly explains whether $this->config, self::config, or static::config is appropriate and reflects the confirmed usage.
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
- 45/100