I often find the universal search to be inadequate. If I am running a process on a large project and want to immediately find where in the code printed out a log statement to console, how can I easily find it? The search only seems to search annotation related marks and not the actual log statement itself.
Maybe I need to start indicating the file in each log print, but that sounds tedious. Maybe a custom activity could help? Any thoughts?
Additionally sometimes I’ll see an error to something of this nature " Assign: failed" but it again has no way to search to find it unless I go through and give each Assign activity a unique header name next to “Assign”. Is there a way to make a custom activity or something to automatically add a unique searchable value (or just copy the variable name in header) for me to save the time waste?
Perhaps I’ll just have to wait until the powers at be stumble across the brilliant idea to just add a control click function to console output to immediately take me to that location.