Chromium Code Reviews| OLD | NEW |
|---|---|
| (Empty) | |
| 1 # Code structure | |
| 2 | |
| 3 * [analysis](analysis): Core of analysis for Chrome crashes. | |
|
wrengr
2016/11/10 21:20:35
-> "Core library for analyzing Chrome crashes."
stgao
2016/11/14 23:30:51
Done.
| |
| 4 * [app](app): The App Engine modules to provide core services of Predator. | |
|
wrengr
2016/11/10 21:20:35
-> "The AppEngine application for invoking the lib
stgao
2016/11/14 23:30:51
Done. Removed "modules" and "services" as they mig
| |
| 5 | |
| 6 # Refactoring guideline | |
| 7 * All core logic of analysis should live in [analysis](analysis), and it should | |
| 8 be standalone, and not depend any App Engine APIs. | |
| 9 * All app-layer code should live in [app](app) | |
| 10 * Frontend code rendering UIs to providing APIs for clients like | |
| 11 ClusterFuzz/Fracas/Cracas should live in [app/frontend](app/frontend). | |
| 12 * Backend code running the analysis should live in [app/backend](app/backend). | |
| 13 * Shared code between the frontend and backend should live in [app/common](app /common). | |
| 14 | |
| 15 # Next step | |
| 16 When the refactoring is done, we will do a one-off move to appengine/predator. | |
| OLD | NEW |