Sha256: eb75e2d8d32160fa541c1bdcef0b86f8e902cf82c9e60533e2c5b129219579ef
Contents?: true
Size: 1.52 KB
Versions: 185
Compression:
Stored size: 1.52 KB
Contents
--- name: New Feature Suggestion about: Want to add a feature to Jets? title: '' labels: feature assignees: '' --- <!-- Hi! Thanks for considering to file a feature request with Jets. Please take the time to answer the basic questions. Please try to be as detailed as possible. Thanks! --> ## Summary <!-- A one-paragraph explanation of the feature. --> ## Motivation <!-- Why do you want to see this feature in Jets? What use cases does it support? How the feature would be relevant to 80% or more of Jets users. --> ## Guide-level explanation <!-- Explain the proposal as if it was already included in the project and you were teaching it to another programmer. That generally means: - Introducing new named concepts. - Explaining the feature largely in terms of examples. - If applicable, provide sample error messages, deprecation warnings, or upgrade guidance. If this is a small feature, you may omit this section. --> ## Reference-level explanation <!-- This is the technical portion of the feature request. Explain the design in sufficient detail that: - Its interaction with other features is clear. - It is reasonably clear how the feature would be implemented. - Corner cases are dissected by example. If you do not know how to answer this, you can omit it. No worries! --> ## Drawbacks <!-- Why should we *not* do this? --> ## Unresolved Questions <!-- What related issues do you consider out of scope for this feature that could be addressed in the future independently of the solution that comes out of this feature? -->
Version data entries
185 entries across 185 versions & 4 rubygems