You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we have no straightforward way of printing SearchResult markers when running via our build plugins.
This means that search recipes run but produce no visible output.
As a first step to fixing this, we need to have a default SearchResultPrinter for each type of SourceFile. These default search result printers must print markers inside of a context-appropriate comment so that reifying the markers to code changes doesn't result in broken code. e.g.: /* ~~> */ for Java and <!-- ~~> --> for XML
The text was updated successfully, but these errors were encountered:
Currently we have no straightforward way of printing SearchResult markers when running via our build plugins.
This means that search recipes run but produce no visible output.
As a first step to fixing this, we need to have a default SearchResultPrinter for each type of SourceFile. These default search result printers must print markers inside of a context-appropriate comment so that reifying the markers to code changes doesn't result in broken code. e.g.:
/* ~~> */
for Java and<!-- ~~> -->
for XMLThe text was updated successfully, but these errors were encountered: