phoedos/pmd
1
1
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Document #1938 in migration guide

Browse Source
This commit is contained in:
Clément Fournier
2020-10-26 18:30:21 +01:00
parent 0a4dd810c9
commit 27441ae3dc
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/pages/pmd/userdocs/extending/writing_xpath_rules.md
View File

@ -127,6 +127,18 @@ represented by our 1.0 implementation as strings, meaning that `@BeginLine > "1"
worked ---that's not the case in 2.0 mode.
* <code>@ArgumentCount > <b style="color:red">'</b>1<b style="color:red">'</b></code> &rarr; `@ArgumentCount > 1`
* In XPath 1.0, the expression `/Foo` matches the *children* of the root named `Foo`.
In XPath 2.0, that expression matches the root, if it is named `Foo`. Consider the following tree:
```java
Foo
└─ Foo
└─ Foo
```
Then `/Foo` will match the root in XPath 2, and the other nodes (but not the root) in XPath 1.
See eg [an issue caused by this](https://github.com/pmd/pmd/issues/1919#issuecomment-512865434) in Apex,
with nested classes.
## Rule properties
**See [Defining rule properties](pmd_userdocs_extending_defining_properties.html#for-xpath-rules)**