- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for api (0.12 sec)
-
.github/ISSUE_TEMPLATE/feature_enhancement_request.yaml
features down to compact but powerful abstractions, and controlling feature bloat carefully. - type: textarea attributes: label: API(s) description: Which existing classes or methods do you want to improve? placeholder: e.g., `com.google.common.collect.ImmutableList::of` render: java validations: required: true
Others - Registered: Fri May 03 12:43:13 GMT 2024 - Last Modified: Fri Nov 17 18:47:47 GMT 2023 - 3.9K bytes - Viewed (0) -
.github/workflows/scorecard.yml
# repo_token: ${{ secrets.SCORECARD_TOKEN }} # Public repositories: # - Publish results to OpenSSF REST API for easy access by consumers # - Allows the repository to include the Scorecard badge. # - See https://github.com/ossf/scorecard-action#publishing-results. # For private repositories:
Others - Registered: Fri May 03 12:43:13 GMT 2024 - Last Modified: Mon Apr 29 23:37:56 GMT 2024 - 2.9K bytes - Viewed (0) -
.github/ISSUE_TEMPLATE/feature_addition_request.yaml
value: > Comparing two approaches to a use case side by side can make it easier to examine the differences between them. Additionally, it's very useful to us if you can provide a "straw API" — what the method signatures would look like, for example, even if the method and class names are still in flux. This can make the feature you're suggesting much clearer to us. - type: textarea
Others - Registered: Fri May 03 12:43:13 GMT 2024 - Last Modified: Fri Nov 17 18:47:47 GMT 2023 - 5.8K bytes - Viewed (0)