-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: scaffold pricing module lib #28
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to add an interface that will be used by the consumers of this module. The CoingeckoService
should implement this interface. It could be named IPricingService
, for example. This will ensure that the pricing service is easily replaceable with any provider in the future.
|
||
@Injectable() | ||
export class CoingeckoService implements IPricingService { | ||
private readonly API_BASE_URL = "https://api.coingecko.com/api/v3/"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wdyt if we remove this hardcoded value and ask for 2 parameters baseUrl
and apiKey
instead???
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
okayy sound good to me
I'll setup the ConfigService in a different PR according to what we discussed in DM, injecting ConfigService instead of raw value |
🤖 Linear
Closes ZKS-63
Description
Scaffold Pricing module library:
CoingeckoService