[
https://jira.jboss.org/jira/browse/JBIDE-3290?page=com.atlassian.jira.plu...
]
Alexey Kazakov commented on JBIDE-3290:
---------------------------------------
> But why did we even start not filtering ? Which usecase/problem
were we solving with this ?
It's hard to found particular issues in jira but we certainly had some critical ones.
And filtering was implemented differently in JSF and Seam EL CA.
And even when this filtering worked it inserted proposals in wrong place for some cases.
When we stoped filter EL for strings without #{} our CA became muche stable and
predictable.
The only way to implement this feature now is to implement some temporary patches for JSF
and Seam EL CAs.
I believe it will cause some new issues for other usecases.
We can't solve it properly now because of shortage of time.
The only possible way to solve this problem for 3.0.0 is to try to up styles proposals and
leave unfiltered EL in the end of the list. But we need investigate whether it is possible
or not for this usecase.
> The idea about merging the completion was to get *better*
completion not worse ;)
Sure :)
But we have not finished this work yet. We had implemented only some first steps.
The next ones are
https://jira.jboss.org/jira/browse/JBIDE-2920 and
https://jira.jboss.org/jira/browse/JBIDE-2808
During implementing them we must to gather all demanded rules for CA and implement it in
new CA Processors.
Without it we can't solve such bugs properly.
sorting/filtering is not updating correctly in code completion of
source page in VPE
------------------------------------------------------------------------------------
Key: JBIDE-3290
URL:
https://jira.jboss.org/jira/browse/JBIDE-3290
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 3.0.0.cr1
Reporter: Max Rydahl Andersen
Assignee: Victor Rubezhny
Priority: Critical
Fix For: 3.0.0.cr1
The sorting seem to make all EL completion show above the more relevant properties of
style attributes and when typing the EL completion stays there even though they do not
match the filter.
See attached video
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira