Chromium Code Reviews| OLD | NEW |
|---|---|
| (Empty) | |
| 1 # Code structure | |
| 2 | |
| 3 * [analysis](analysis): Core library for analyzing Chrome crashes. | |
| 4 * [app](app): The App Engine app to provide web APIs to analyze Chrome crashes t hrough invoking the core library above, and web pages to view & monitor analysis results. | |
|
wrengr
2016/11/15 00:38:01
nit: line too long
stgao
2016/11/16 18:44:11
This is OK for text file, but not for code file.
| |
| 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 ClusterFuzz/F racas/Cracas should live in [app/frontend](app/frontend). | |
| 11 * Backend code running the analysis should live in [app/backend](app/backend). | |
| 12 * Shared code between the frontend and backend should live in [app/common](app /common). | |
| 13 | |
| 14 # Next step | |
| 15 When the refactoring is done, we will do a one-off move to appengine/predator. | |
| OLD | NEW |