Skip to content

fix: handle non standard currency with decoded length of 3#1131

Merged
pdp2121 merged 6 commits intostagingfrom
handle-fake-xrp
Feb 25, 2025
Merged

fix: handle non standard currency with decoded length of 3#1131
pdp2121 merged 6 commits intostagingfrom
handle-fake-xrp

Conversation

@pdp2121
Copy link
Collaborator

@pdp2121 pdp2121 commented Feb 19, 2025

High Level Overview of Change

Handle non standard currency that decoded to 3 characters, putting prefix Fake to such currency.

Instead of being non-standard, 3 character currency codes should use the standard format if they are not "fake".

Context of Change

Resolve #1130

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Refactor (non-breaking change that only restructures code)
  • Tests (You added tests for code that already exists, or your new feature included in this PR)
  • Documentation Updates
  • Translation Updates
  • Release

Before / After

Before

Screenshot 2025-02-19 at 4 06 15 PM

After

Screenshot 2025-02-19 at 4 07 00 PM

@intelliot intelliot changed the title fix: handle non standard currency with decoded length less than 4 fix: handle non standard currency with decoded length of 3 Feb 22, 2025
@pdp2121 pdp2121 merged commit 79892cb into staging Feb 25, 2025
4 checks passed
@pdp2121 pdp2121 deleted the handle-fake-xrp branch February 25, 2025 16:55
mvadari pushed a commit that referenced this pull request Apr 7, 2025
## High Level Overview of Change

<!--
Please include a summary/list of the changes.
If too broad, please consider splitting into multiple PRs.
-->
Handle non standard currency that decoded to 3 characters, putting
prefix `Fake` to such currency.

Instead of being non-standard, 3 character currency codes should use the
[standard
format](https://xrpl.org/docs/references/protocol/data-types/currency-formats#standard-currency-codes)
if they are not "fake".

### Context of Change

<!--
Please include the context of a change.
If a bug fix, when was the bug introduced? What was the behavior?
If a new feature, why was this architecture chosen? What were the
alternatives?
If a refactor, how is this better than the previous implementation?

If there is a design document for this feature, please link it here.
-->
Resolve #1130

### Type of Change

<!--
Please check relevant options, delete irrelevant ones.
-->

- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] Refactor (non-breaking change that only restructures code)
- [ ] Tests (You added tests for code that already exists, or your new
feature included in this PR)
- [ ] Documentation Updates
- [ ] Translation Updates
- [ ] Release

## Before / After

<!--
If just refactoring / back-end changes, this can be just an in-English
description of the change at a technical level.
If a UI change, screenshots should be included.
-->

### Before

<img width="941" alt="Screenshot 2025-02-19 at 4 06 15 PM"
src="https://github.com/user-attachments/assets/f7df4ce9-942e-4274-b7ea-39050b976456"
/>

### After

<img width="952" alt="Screenshot 2025-02-19 at 4 07 00 PM"
src="https://github.com/user-attachments/assets/95e46ee3-01c7-425d-a0ca-d2e584eccb76"
/>

---------

Co-authored-by: Elliot Lee <github.public@intelliot.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Handle non-standard currency code "XRP"

4 participants