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 196357 - PHP code completion does not work when error exists in code
Summary: PHP code completion does not work when error exists in code
Status: NEW
Alias: None
Product: php
Classification: Unclassified
Component: Editor (show other bugs)
Version: 7.0
Hardware: All All
: P2 normal with 2 votes (vote)
Assignee: Ondrej Brejla
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-05 18:19 UTC by lucifurious
Modified: 2013-11-19 03:18 UTC (History)
3 users (show)

See Also:
Issue Type: TASK
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 lucifurious 2011-03-05 18:19:42 UTC 
Product Version = NetBeans IDE Dev (Build 201103040000)
Operating System = Linux version 2.6.35-25-generic running on amd64
Java; VM; Vendor = 1.6.0_24
Runtime = Java HotSpot(TM) 64-Bit Server VM 19.1-b02

This is very annoying and should be pretty simple to correct.

When you have an error in your current PHP file, code completion (ctrl-click function name, etc.) does not work. Not until you clear your error does the click work. 

My use case: I frequently will copy/paste code from another project or something and it may not yet be completely integrated into my current file. While this fragment exists that may or may not be valid, code completion is non-functional.
Comment 1 Petr Pisl 2011-03-09 13:48:29 UTC 
The code completion is context sensitive. When you paste a code with an error the code completion can not find probably the right context. It depends how much is the code wrong. Probably there could be better resolving such situations.
Comment 2 Petr Pisl 2011-03-17 09:04:35 UTC 
I'm switching this defect to the task. The current situation is there from NB 6.5 and should be improved as a complex task.
Comment 3 Marian Mirilovic 2011-03-17 10:56:26 UTC 
Petr, I really do not think this kind of issue can be a task. If you are not going to fix it in 7.0 (as I assume), ask for a waiver. But I think issues like this should be delivered in NB 7.0.1 (Dev)
Comment 4 Petr Pisl 2011-03-18 13:23:15 UTC 
Marian, this is here from 6.5. The situation is not ideal, but this is the first complain. There has to be created a strong heuristic that will correct the wrong code. This is not issue for one week. You have to cover thousands cases. How many cases have to be fixed to mark it as fixed? 10 ? 100? 1000? If you give me a number, it's ok. But this issue is to abstract to provide a concrete fix.
Comment 5 Marian Mirilovic 2011-03-18 14:19:38 UTC 
(In reply to comment #4)
> the wrong code. This is not issue for one week. You have to cover thousands
> cases. How many cases have to be fixed to mark it as fixed? 10 ? 100? 1000? If
> you give me a number, it's ok. But this issue is to abstract to provide a
> concrete fix.

Ok, I understand and added WAIVER for 7.0. 

From my point of view as many as possible. I am not saying all of them must be fixed into next release. I think we can probably exchange it to many small defects and keep this one as umbrella. But would be nice to fix at least some of them into next release.
Comment 6 Petr Pisl 2011-05-19 09:23:44 UTC 
Still there is a lot of work on this. IMHO should be more task.
Comment 7 Tomas Mysik 2011-06-01 20:19:24 UTC 
Reassigning, thanks.
Comment 8 Petr Pisl 2011-06-20 11:54:45 UTC 
I'm trying to mark this issue as a task. There has to be done more work and it doesn't have sense to wave it a few years.