fix: correct readme instructions on how to access fiat methods #173
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
oh thank you. |
My pleasure @bumi . Do let me know if there's any other way I can be of service |
rolznz
approved these changes
Nov 20, 2024
|
Thanks @Toheeb-Ojuolape ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this? (check all applicable)
Description
This PR implements corrections to the fiat examples in the README by ensuring that an object is being passed to the fiat methods. It also shows users the correct way of using the getFiatValue, getSatoshiValue and getFormattedFiatValue as they cannot be imported directly from the @getalby/lightning-tools without first importing { fiat }
Related Tickets & Documents
Resolves #128