Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 371311

Summary: [Search]De-couple in-file-search and replace APIs from searchResultModel.
Product: [ECD] Orion Reporter: libing wang <libingw>
Component: ClientAssignee: libing wang <libingw>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: 0.4   
Target Milestone: 0.4 RC1   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Bug Depends on:    
Bug Blocks: 368871    

Description libing wang CLA 2012-02-11 13:52:14 EST 
In RC2, I planned some more unit tests on the so called "in file search" and "replace selected matches" APIs.
Theses APIs are now tightly bundled with searchResultModel, which is consumed by the explorer-render-model pattern.

In the unit test, we basically need a file contents and a search string(either literal or wild card). Then in the unit tests we will ask the de-coupled APIs to generate a file node(just an object) with all matches attached. We can then use the fie node and the replacing string to generate the replaced contents.
These APIs should not rely on any explorer-render-model pattern.