Download the PHP package rg/phpnsc without Composer
On this page you can find all versions of the php package rg/phpnsc. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package phpnsc
phpnsc
The PHP namespace checker, checks all files in a project for invalid class references.
It prints an error, if a class was used with it's simple or relative name but is:
- not in the same namespace
- or not in the corresponding sub namespace
- or does not have a corresponding use statement
Usage
- Add a JSON config file to your project root (see
config.sample.json) - Run phpnsc:
Configuration
The configuration has to be in a JSON file, that usually is placed in the root of your project. Example:
- sources: list of source folders to be scanned
- vendor: specifies the root vendor namespace of your project, see (https://gist.github.com/1234504)
- folders/root: the root folder of your project
- include: which sub-folders of your project root should be included?
- exclude: are there be any sub-sub-folders that should be excluded?
- filetypes: file types that should be included and excluded from analysis
- output: array of output classes that should be used. Currently support are:
- CheckstyleOutput (checkstyle compatible XML file, e.g. for a CI server)
- ConsoleOutput
How it works
First the tool scans for all files matching the criteria defined in the config file. For each file it strips out all unnecessary stuff like comments, strings or non php content. After that it analyzes all defined classes and interfaces in your project and all used and referenced classes and interfaces in each file based on regular expressions. In the next step, it then uses this information to deduct if all classes and interfaces are referenced correctly.
Current limitations
This tool is still alpha. It is certainly possible, that it does not find all errors of that it finds false positives. Additionally it can not handle importing several namespaces with one use statement and may have problems with using aliases.
