You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*[Cooperation with IntelliJ plugin](#cooperation-with-intellij-plugin)
9
10
10
11
## Overview
11
12
Phases increase configurability. Rule implementations are defined as a list of phases. Each phase defines a specific step, which helps breaking up implementation into smaller and more readable groups. Some phases are independent from others, which means the order doesn't matter. However, some phases depend on outputs of previous phases, in this case, we should make sure it meets all the prerequisites before executing phases.
@@ -144,9 +145,36 @@ Files in `scala/private/phases/`
144
145
-`phase_<PHASE_NAME>.bzl`: phase definition file
145
146
146
147
Function names in `phase_<PHASE_NAME>.bzl`
147
-
-`phase_<RULE_NAME>_<PHASE_NAME>`: function with custom inputs of specific rule
148
-
-`phase_common_<PHASE_NAME>`: function without custom inputs
149
-
-`_phase_default_<PHASE_NAME>`: private function that takes `_args` for custom inputs
148
+
-`phase_<PHASE_NAME>_<RULE_NAME>`: function with custom inputs of specific rule
149
+
-`phase_<PHASE_NAME>_common`: function without custom inputs
150
+
-`_phase_<PHASE_NAME>_default`: private function that takes `_args` for custom inputs
150
151
-`_phase_<PHASE_NAME>`: private function with the actual logic
151
152
152
153
See `phase_compile.bzl` for example.
154
+
155
+
## Cooperation with IntelliJ plugin
156
+
157
+
Bazel IntelliJ plugin has hard-coded the names of rules_scala targets that it detects as Scala targets:
0 commit comments