XPathView - features requests

Hi Sasha.

Our projects contain 2 independent roots of XSL files - shared and specific for particular project. (These merged into single one during deployment.)

As result all shared templates calls from project specific XSL files are highlighted as red because validator can't resolve relative HREFs (e.g. ../../editors.xsl) if this file is from other root.

I understand it is too hard to implement multiple roots support. But probably it is easy to implement small improvements:

1) at the moment syntax highlighting, IntellySense and validation are turned on/off by "Enabled" check box - could you please introduce separate check box for each feature?

2) Some validations can be suppressed (e.g. "Make type conversion explicit") using Inspect code profiles dialog (XPath node). But there are warnings which I can't switch off: "Missing template parameter", "Unresolved variable" and "Can't resolve template" - couild you please add these rules to Inspection code profiles dialog?

Regards, Alexander Pavlov

1 comment

Hello Alexander,

thanks for your feedback.

I understand it is too hard to implement multiple roots support. But probably
it is easy to implement small improvements:


I'd actually like to implement that, but I don't know yet how the configuration
would look like and if IDEA can be convinced to lookup a relative file path
under different base-paths without re-inventing the wheel. I'll definitely
consider this, but probably not in the nearest future.

1) at the moment syntax highlighting, IntellySense and validation are turned
on/off by "Enabled" check box - could you please introduce separate check box
for each feature?


This is very unlikely to happen. The "Enabled" option is just some kind of a
maintenance setting that allows the user to temporarily disable the plugin in
case it causes any problems. I don't believe there's much value in offering
different levels of "enabled", apart from maybe a way to make the highlighting
more configurable - see below.

2) Some validations can be suppressed (e.g. "Make type conversion explicit")
using Inspect code profiles dialog (XPath node). But there are warnings which
I can't switch off: "Missing template parameter", "Unresolved variable" and
"Can't resolve template" - couild you please add these rules to Inspection
code profiles dialog?


Well, the basic rule is that things that either violate (unresolved variable) or
overly bend (missing or superfluous parameter) the XSLT standard are highlighted
like the same kind of things as in Java code and XML - which can't be suppressed
either. I'll think of a way to relax this for situations like yours.

Sascha

0

Please sign in to leave a comment.