[Extensions] Allow multiple feature registration methods
Currently, we have a single generated class that registers all the extension features in the constructor. For instance, ChromeAPIFeatureProvider registers both features from both //chrome and //extensions. Refactor this to generate a method that takes a FeatureProvider and adds features to it, rather than generating a FeatureProvider subclass. This allows us to have multiple feature registration methods called for a single provider, rather than needing a single class per build. This is necessary in order to split out app and extension feature registration. Bug: 862310 Change-Id: I9fba5ea57d8b14ca9f893a2694661163c8bc4140 Reviewed-on: https://chromium-review.googlesource.com/1132124Reviewed-by:Stephen Lanham <slan@chromium.org> Reviewed-by:
Albert Chaulk <achaulk@chromium.org> Reviewed-by:
Istiaque Ahmed <lazyboy@chromium.org> Commit-Queue: Devlin <rdevlin.cronin@chromium.org> Cr-Commit-Position: refs/heads/master@{#575018}
Showing
Please register or sign in to comment