- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 14 for unchecked (0.21 sec)
-
build-logic/binary-compatibility/src/main/groovy/gradlebuild/binarycompatibility/rules/UpgradePropertiesRulePostProcess.java
public class UpgradePropertiesRulePostProcess implements PostProcessViolationsRule { @Override @SuppressWarnings("unchecked") public void execute(ViolationCheckContextWithViolations context) { Set<AccessorKey> seenUpgradedAccessorsChanges = (Set<AccessorKey>) context.getUserData().get(SEEN_OLD_ACCESSORS_OF_UPGRADED_PROPERTIES);
Java - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Tue Apr 23 08:40:36 GMT 2024 - 3.4K bytes - Viewed (0) -
build-logic-commons/gradle-plugin/src/main/kotlin/gradlebuild.cache-miss-monitor.gradle.kts
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. */ @file:Suppress("UNCHECKED_CAST") import gradlebuild.AbstractBuildScanInfoCollectingService import gradlebuild.registerBuildScanInfoCollectingService import org.gradle.tooling.events.task.TaskOperationResult
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Thu Mar 07 05:49:29 GMT 2024 - 4.6K bytes - Viewed (0) -
build-logic/jvm/src/main/kotlin/gradlebuild.unittest-and-compile.gradle.kts
// Undo: https://github.com/JetBrains/teamcity-gradle/blob/e1dc98db0505748df7bea2e61b5ee3a3ba9933db/gradle-runner-agent/src/main/scripts/init.gradle#L818 if (project.hasProperty("teamcity")) { @Suppress("UNCHECKED_CAST") val teamcity = project.property("teamcity") as MutableMap<String, Any> teamcity["teamcity.build.tempDir"] = "" } }
Plain Text - Registered: Wed Mar 27 11:36:08 GMT 2024 - Last Modified: Wed Jan 17 13:36:27 GMT 2024 - 15.7K bytes - Viewed (0) -
.cm/lacks_tests.cm
# can also use the constant `true` if you want to always run the actions. # Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 2.4K bytes - Viewed (0) -
.cm/add_usual_expert.cm
# can also use the constant `true` if you want to always run the actions. # Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.4K bytes - Viewed (0) -
.cm/complex_changes.cm
# can also use the constant `true` if you want to always run the actions. # Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.7K bytes - Viewed (0) -
.cm/estimated_time_to_review.cm
# can also use the constant `true` if you want to always run the actions. # Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 2K bytes - Viewed (0) -
.cm/platform_labels.cm
# can also use the constant `true` if you want to always run the actions. # Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Mon Apr 22 15:32:31 GMT 2024 - 2.5K bytes - Viewed (0) -
.cm/misc_labels.cm
# can also use the constant `true` if you want to always run the actions. # Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 3K bytes - Viewed (0) -
.cm/summary_table.cm
# can also use the constant `true` if you want to always run the actions. # Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed Apr 17 11:36:08 GMT 2024 - Last Modified: Thu Feb 08 15:20:44 GMT 2024 - 6.5K bytes - Viewed (0)