Open import-brain opened 2 years ago
IDK, crypto()
could fit into the finance
module and hashAlorythm()
in the hacker
module. I don't see the need for a new module.
IDK,
crypto()
could fit into thefinance
module andhashAlorythm()
in thehacker
module. I don't see the need for a new module.
That is exactly my same thought when I read this PR initially. Really not sure if a new module is worth it for this.
IDK,
crypto()
could fit into thefinance
module andhashAlorythm()
in thehacker
module. I don't see the need for a new module.That is exactly my same thought when I read this PR initially. Really not sure if a new module is worth it for this.
Yeah, should I change this issue to "implement finance.crypto() and hacker.hashAlgorithm()"? Should I make another issue? Should those two functions be in separate issues?
Currently I dont see a usecase for any of these. What are the user going to do with them? Just because we can generate certain data doesnt mean we should.
Yeah, should I change this issue to "implement finance.crypto() and hacker.hashAlgorithm()"? Should I make another issue? Should those two functions be in separate issues?
Yeah, maybe even better finance.blockchainCrypto()
or something else?
Currently I dont see a usecase for any of these. What are the user going to do with them? Just because we can generate certain data doesnt mean we should.
@import-brain It is always good to also provide a cause why you want to implement something.
Currently I dont see a usecase for any of these. What are the user going to do with them? Just because we can generate certain data doesnt mean we should.
The use case is narrower than most other functions, but I think it would be helpful to generate cryptocurrency visualizations and chart websites, like this.
For example, if .crypto()
returned an object with the coin's logo, name, and symbol, a user could call the function multiple times and map the results into cards for testing purposes to ensure the card components they wrote work as expected.
Thank you for your feature proposal.
We marked it as "waiting for user interest" for now to gather some feedback from our community:
If you would like to see this feature be implemented, please react to the description with an up-vote (:+1:).
If you have a suggestion or want to point out some special cases that need to be considered, please leave a comment, so we are aware about them.
We would also like to hear about other community members' use cases for the feature to give us a better understanding of their potential implicit or explicit requirements.
We will start the implementation based on:
the number of votes (:+1:) and comments
the relevance for the ecosystem
availability of alternatives and workarounds
and the complexity of the requested feature
We do this because:
There are plenty of languages/countries out there and we would like to ensure that every method can cover all or almost all of them.
Every feature we add to faker has "costs" associated to it:
hey guys. making a simple trading app for logging my trades. I'd love to have a way to seed database with coin symbols, coin names and coin pairs. A way to specify kind of coin: stable coins and alts/btc, would be really nice. smth like that maybe faker.finance.crypto({ stable?: boolean })
@bnn1 Then please upvote the issue, so we are able to track community interest better.
Clear and concise description of the problem
I wish to be able to use Faker to be able to generate random cryptocurrency and blockchain related entries.
Suggested solution
faker.blockchain.crypto() // { name: "Cardano", symbol: "ADA" }
faker.blockchain.crypto() // { name: "Ripple", symbol: "XRP" }
As you can see, forblockchain.crypto()
, the backend should work pretty similarly to the functions inscience
.faker.blockchain.hashAlgorithm() // "SHA-256"
faker.blockchain.hashAlgorithm() // "X11"
In addition, deprecate the
finance.bitcoinAddress()
,finance.ethereumAddress()
, andfinance.litecoinAddress()
functions and move them to the blockchain module.Alternative
No response
Additional context
No response