mirror of
https://github.com/jenkinsci/jenkins.git
synced 2026-11-10 02:26:18 +00:00
supported more complex relative path
This commit is contained in:
1 parent
d72a9a2bc5
commit
17317bb4ca
2 files changed
+37
-7
No files matched your search
@@ -14,8 +14,23 @@ import static java.lang.annotation.RetentionPolicy.*;
|
||||
* nearby parameters that belong to different parents.
|
||||
*
|
||||
* <p>
|
||||
* Currently, "..", "../..", etc. are supported to indicate
|
||||
* parameters that belong to the ancestors.
|
||||
* ".." refers
|
||||
* to values in the parent object, and "foo" refers to the child
|
||||
* object of the current object named "foo". They can be combined
|
||||
* with '/' like path, such as "../foo/bar", "../..", and etc.
|
||||
*
|
||||
* <p>
|
||||
* A good way to think about this is the file system structure.
|
||||
* {@code @RelativePath} is like the dirname, and {@code QueryParameter}
|
||||
* is like the basename. Together they form a relative path.
|
||||
* And because of the structured form submissions,
|
||||
* form elements are organized in a tree structure of JSON objects,
|
||||
* which is akin to directories and files.
|
||||
*
|
||||
* <p>
|
||||
* The relative path then points from the current input element
|
||||
* (for which you are doing form validation, for example) to the target
|
||||
* input element that you want to obtain the value.
|
||||
*
|
||||
* @author Kohsuke Kawaguchi
|
||||
* @since 1.376
|
||||
|
||||
Reference in new issue
Block a user