Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 28 for function (0.3 sec)

  1. .cm/plugins/filters/categorize/index.js

     * @returns {[Object]} Returns a list of objects for each platform containing info about the changes to files in that platform
     * @example {{ owners | categorize(branch.diff.files_metadata) }}
     */
    
    function categorize(fileOwners, fileMetadatas) {
        const result = new Map();
        [...fileOwners.keys()].forEach(platform => {
            result.set(platform, {
                name: platform,
                files: []
            });
    JavaScript
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 1.2K bytes
    - Viewed (0)
  2. .cm/estimated_time_to_review.cm

    # 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 01 11:36:15 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 2K bytes
    - Viewed (0)
  3. build-logic/kotlin-dsl-shared-runtime/src/main/kotlin/org/gradle/kotlin/dsl/internal/sharedruntime/codegen/ApiTypeProvider.kt

                ?: Type.getArgumentTypes(delegate.desc).map { it.className }
            val names by unsafeLazy {
                parameterNamesFor(
                    function.owner.sourceName,
                    function.name,
                    parameterTypesBinaryNames
                )
            }
            parameterTypesBinaryNames.mapIndexed { idx, parameterTypeBinaryName ->
    Plain Text
    - Registered: Wed Feb 28 11:36:09 GMT 2024
    - Last Modified: Tue Feb 06 19:56:10 GMT 2024
    - 20.8K bytes
    - Viewed (0)
  4. .cm/add_usual_expert.cm

    # 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 01 11:36:15 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 1.4K bytes
    - Viewed (0)
  5. .cm/complex_changes.cm

    # 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 01 11:36:15 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 1.7K bytes
    - Viewed (0)
  6. .cm/plugins/filters/nullToEmpty/index.js

     * @param {Object} input - The object to investigate
     * @returns Object - The specified value if non-null, otherwise an empty array
     * @example {{ readField('jvm', 'files') | nullToEmpty }}
     */
    function nullToEmpty(input) {
        let output;
        if (input) {
            output = input;
        } else {
            output = [];
        }
        console.log("nullToEmpty: " + output);
        return output;
    }
    
    JavaScript
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Mon Apr 22 16:43:16 GMT 2024
    - 526 bytes
    - Viewed (0)
  7. .cm/platform_labels.cm

    # 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 01 11:36:15 GMT 2024
    - Last Modified: Mon Apr 22 15:32:31 GMT 2024
    - 2.5K bytes
    - Viewed (0)
  8. .cm/misc_labels.cm

    # 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 01 11:36:15 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 3K bytes
    - Viewed (0)
  9. .cm/summary_table.cm

    # 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)
  10. build-logic/binary-compatibility/src/main/groovy/gradlebuild/binarycompatibility/rules/UpgradePropertiesRuleSetup.java

    import me.champeau.gradle.japicmp.report.ViolationCheckContext;
    
    import java.util.AbstractMap;
    import java.util.HashSet;
    import java.util.List;
    import java.util.Map;
    import java.util.function.Function;
    import java.util.stream.Collectors;
    import java.util.stream.Stream;
    
    import static gradlebuild.binarycompatibility.upgrades.UpgradedProperties.CURRENT_ACCESSORS_OF_UPGRADED_PROPERTIES;
    Java
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Tue Apr 23 08:40:36 GMT 2024
    - 4.2K bytes
    - Viewed (0)
Back to top