Anonymous | Login | Signup for a new account | 2023-03-20 06:10 EDT | ![]() |
My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0000417 | JANA | Feature Request | public | 2014-09-29 07:30 | 2015-06-01 15:54 | ||||
Reporter | davidl | ||||||||
Assigned To | davidl | ||||||||
Priority | normal | Severity | minor | Reproducibility | N/A | ||||
Status | resolved | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Summary | 0000417: Add GetRecursive method to JObject | ||||||||
Description | It would be useful to be able to ask JANA to not only search associated objects, by the associated objects of each associated object when looking for a specific type. e.g. asking a DBCALHit for the Df250PulseIntegral it is associated with. Care would need to be taken not to run into an infinite loop. An optional parameter would probably also be needed to allow the caller to specify a maximum depth. | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||
![]() |
|
(0000632) davidl (administrator) 2015-06-01 15:54 |
This was added in revision 2322 and will appear in JANA 0.7.3. This was actually added to the already existing Get() method and an optional parameter added to that call to specify the maximum depth of associations to check. This is set to a very large number by default so that for practical purposes, all levels are checked. To get the original behavior of only checking direct descendants,, users must specify max_depth=1. |
![]() |
|||
Date Modified | Username | Field | Change |
2014-09-29 07:30 | davidl | New Issue | |
2014-12-03 06:22 | davidl | Status | new => assigned |
2014-12-03 06:22 | davidl | Assigned To | => davidl |
2015-06-01 15:54 | davidl | Note Added: 0000632 | |
2015-06-01 15:54 | davidl | Status | assigned => resolved |
2015-06-01 15:54 | davidl | Resolution | open => fixed |
Copyright © 2000 - 2023 MantisBT Team |