The search box is a central element of the Code Search UI (see Figure 17-1), and like web search, it has "suggestions" that developers can use for quick navigation to files, symbols, or directories. In this chapter, we’ll look at Code Search in more detail, including how Googlers use it as part of their developer workflows, why we chose to develop a separate web tool for code searching, and examine how it addresses the challenges of searching and browsing code at Google repository scale. To do so, it relies heavily on cloud-based backends for searching content and resolving cross-references. In contrast to integrated development environments (IDEs) or code editors, Code Search is optimized for the use case of reading, understanding, and exploring code at scale. That integration changed its focus from searching to browsing code, and later development of Code Search was partly guided by a principle of "answering the next question about code in a single click." Now such questions as "Where is this symbol defined?", "Where is it used?", "How do I include it?", "When was it added to the codebase?", and even ones like "Fleet-wide, how many CPU cycles does it consume?" are all answerable with one or two clicks. 2 Its place as a key tool for Google developers was cemented by the integration of Kythe/Grok, 3 which added cross-references and the ability to jump to symbol definitions.
Code Search began as a combination of a grep-type tool 1 for internal code with the ranking and UI of external Code Search. Like many of the development tools at Google, it arose directly out of a need to scale to the size of the codebase. JohnĬode Search is a tool for browsing and searching code at Google that consists of a frontend UI and various backend elements.
#Google web tool software
Software Engineering at Google Code Search
0 kommentar(er)
