[Feature]: evaluate the value of flavors #76
Labels
state:needs-owner
Needs an issue owner to be assigned
state:needs-triage
Needs to triaged to determine next steps
state:stale
Has not been updated in a long time
type:feature-request
A new feature proposal
urgency:low
Little to no impact
Comments
spbrogan
added
type:feature-request
github-actions
bot
added
urgency:low
|
This issue has been automatically marked as stale because it has not had activity in 45 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions. |
|
This issue has been automatically been closed because it did not have any activity in 45 days and no follow up within 7 days after being marked stale. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Overview
Flavors allowed a creator to trim the functionality to match their needs but flavors added significant complexity and inconsistency to the crypto provider. As we look to scale the crypto binary out more broadly the complexity and incompatibility of flavors is not worth the savings.
Solution Overview
remove flavors and provide more consistent api
Alternatives Considered
No response
Urgency
Low
Are you going to implement the feature request?
Someone else needs to implement the feature
Do you need maintainer feedback?
No maintainer feedback needed
Anything else?
No response
The text was updated successfully, but these errors were encountered: