- Sort Score
- Result 10 results
- Languages All
Results 1 - 6 of 6 for describe (0.17 sec)
-
.github/ISSUE_TEMPLATE/40_contributor_documentation.yml
- Typo (please open a PR instead) validations: required: true - type: textarea id: description attributes: label: Problem description description: | Please describe the problem as concisely as possible. validations: required: true - type: textarea id: context attributes: label: Context (optional) description: |
Others - Registered: Wed Apr 24 11:36:11 GMT 2024 - Last Modified: Mon Jan 15 10:01:01 GMT 2024 - 1.6K bytes - Viewed (0) -
.github/ISSUE_TEMPLATE/50_maintainer_chore.yml
- Refactoring - Other validations: required: true - type: textarea id: description attributes: label: Problem description description: | Please describe the problem as concisely as possible. validations: required: true - type: textarea id: context attributes: label: Context (optional) description: |
Others - Registered: Wed Apr 24 11:36:11 GMT 2024 - Last Modified: Tue Sep 12 11:52:53 GMT 2023 - 856 bytes - Viewed (0) -
architecture/standards/0002-avoid-using-java-serialization.md
Java serialization does not enforce type safety as strictly as some alternatives, potentially leading to runtime errors. ## Decision We do not use Java serialization. Instead, we use custom serialization where we explicitly describe how data objects should be serialized and deserialized. For internal purposes, we use binary formats for their brevity. We use the `Serializer` abstraction to separate the actual implementation of serialization from its uses.
Plain Text - Registered: Wed Apr 24 11:36:11 GMT 2024 - Last Modified: Thu Feb 29 22:32:18 GMT 2024 - 2.3K bytes - Viewed (0) -
architecture-standards/0001-use-architectural-decision-records.md
## Decision The *Build Tool Team* has decided to use Architectural Decision Records (aka ADR) to track decisions we want to follow. The main logic with ADRs is to describe (architectural) decisions made: * To provide best practices and solutions we (as *build tool* team) want to promote. * To avoid asking the same thing multiple times during code review.
Plain Text - Registered: Wed Feb 14 11:36:15 GMT 2024 - Last Modified: Wed Feb 07 00:43:19 GMT 2024 - 2.8K bytes - Viewed (0) -
architecture/standards/0001-use-architectural-decision-records.md
## Decision The *Build Tool Team* has decided to use Architectural Decision Records (aka ADR) to track decisions we want to follow. The main logic with ADRs is to describe (architectural) decisions made: * To provide best practices and solutions we (as the *build tool* team) want to promote. * To avoid asking the same thing multiple times during code review.
Plain Text - Registered: Wed Apr 24 11:36:11 GMT 2024 - Last Modified: Sat Mar 02 21:54:40 GMT 2024 - 2.8K bytes - Viewed (0) -
architecture-standards/0002-avoid-using-java-serialization.md
## Decision We do not use Java serialization. Instead, we use custom serialization where we explicitly describe how data objects should be serialized and deserialized. For internal purposes, we use binary formats for their brevity. We use the `Serializer` abstraction to separate the actual implementation of serialization from its uses.
Plain Text - Registered: Wed Feb 14 11:36:15 GMT 2024 - Last Modified: Thu Feb 08 21:48:27 GMT 2024 - 1.9K bytes - Viewed (0)