This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 230224 - PHP static code analysis setting per project
Summary: PHP static code analysis setting per project
Status: NEW
Alias: None
Product: php
Classification: Unclassified
Component: Code (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal with 1 vote (vote)
Assignee: Tomas Mysik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-24 10:58 UTC by jpd4nt
Modified: 2016-08-19 04:49 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jpd4nt 2013-05-24 10:58:35 UTC 
Can the settings for static code analysis be per project as the projects i deal with use different standards.
Comment 1 Tomas Mysik 2013-05-24 11:41:46 UTC 
@jlahoda: Honzo, do you think that this enhancement is doable?

Thanks.
Comment 2 Tomas Mysik 2014-01-09 07:56:27 UTC 
Thinking about it, I am not sure how it would work because one can create a custom Static Code configuration - what to do if the project has its own configuration as well??
Comment 3 kacer 2016-08-19 04:49:05 UTC 
This could work the same way as already works with test tools.
In project properties add section "Code Analysis" with custom settings for individual tools - "Use Custom Code Sniffer", "Use Custom Standard", etc.

Ability to setup these tools on project level is becoming more important with use of composer - projects can use different versions of tools.