Because we are not integrated with GN yet, we are forced to:
- Manually run the script locally when a change is made.
- Check in generated code
- White-list generated code from linter presubmit scripts (since generated code violates style).
- Ignore unhelpful results in code search/grep
A more viable approach is to only check in source code in the repository and generate the JS/HTML bundles at compile time, based on the target platform and other grit variables.
I have managed to get the overall workflow working for MD Downloads and MD Settings. There are quite a few subtasks to get resolved before all the necessary pieces are in place, so this bug will serve as a tracking bug for all such subtasks.
Current progress:
1) https://codereview.chromium.org/2569283002: Adds GN rules for vulcanize.
2) https://codereview.chromium.org/2569293002: Vulcanize MD Downloads at compile time
3) https://codereview.chromium.org/2573943002: Vulcanize MD Settings at compile time.
Part of this work was originally done by michaelpg at https://codereview.chromium.org/2513673005/.
I will follow up on this bug about subtasks that need to be addressed.
Comment 1 by dpa...@chromium.org
, Dec 13 2016