gavin/maybe
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 28 Wiki Activity

Don't override changed name from plaid #2244

Merged
ahatzz11 merged 1 commits from stop-name-override into main 2025-05-16 23:23:58 +08:00
Conversation 3 Commits 1 Files Changed 1 +4 -1
ahatzz11 commented 2025-05-16 08:10:18 +08:00 (Migrated from github.com)
Copy Link

I've noticed that when I update the name of an account, the next plaid sync will revert the custom name.

I don't have a plaid sandbox (I probably should do this at some point) so I don't have a for sure way to validate this, but I think this should do the trick. If I'm off the right path here, happy to dig further!

I've noticed that when I update the name of an account, the next plaid sync will revert the custom name. I don't have a plaid sandbox (I probably should do this at some point) so I don't have a for sure way to validate this, but I think this should do the trick. If I'm off the right path here, happy to dig further!
Joelute (Migrated from github.com) approved these changes 2025-05-16 09:35:17 +08:00
Joelute (Migrated from github.com) left a comment
Copy Link

Did a quick simple test with Plaid sandbox just now and worked just fine. Changing the name and syncing doesn't override the changed name.

image

Did a quick simple test with Plaid sandbox just now and worked just fine. Changing the name and syncing doesn't override the changed name. ![image](https://github.com/user-attachments/assets/2d6b615f-8636-47d2-99d5-fd257a9cedd8)
ahatzz11 commented 2025-05-16 09:39:26 +08:00 (Migrated from github.com)
Copy Link

Did a quick simple test with Plaid sandbox just now and worked just fine. Changing the name and syncing doesn't override the changed name.

Thanks for the validation @Joelute!

> Did a quick simple test with Plaid sandbox just now and worked just fine. Changing the name and syncing doesn't override the changed name. > Thanks for the validation @Joelute!
zachgoll (Migrated from github.com) approved these changes 2025-05-16 23:23:52 +08:00
zachgoll (Migrated from github.com) left a comment
Copy Link

Yep, this should work! Thanks for the fix.

Yep, this should work! Thanks for the fix.
Sign in to join this conversation.
Reviewers
No Reviewers
Joelute
zachgoll
Labels
Clear labels
📆 Planned
Not ready to be worked on yet, but planned for future
 💻 Self Hosted only
Issues pertaining to self-hosted versions of Maybe
 ⚙️ Config
ℹ️ Needs info
Further information is requested
 📱 Mobile
Bugs exclusively happening on mobile devices
 1️⃣ High Priority
High priority issues will be worked on next
 🚨 Urgent
Issues that are urgent for app functionality
 3️⃣ Low priority
Contributions accepted, but Maybe team will not be working on this in the near term
 2️⃣ Medium Priority
Community contributions accepted, Maybe team only works on if there are no high priority items open
 ⚡ Performance
Performance issues to address
 🎨 UI / UX
Issues related to UI / UX interactions and design.
 💎 Bounty
💰 Rewarded
📊 Data issue
Issues where the app functionally works, but the data is missing or inaccurate.
 🙋 Bounty claim
$1.5K
Community
This is a great issue for community members to work on
 dependencies
Pull requests that update a dependency file
 Design
Hosted only
Hosted app only
 Required self hoster data migration
Self hosters must run data migrations to resolve this issue
 ruby
Pull requests that update Ruby code
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
gavin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: gavin/maybe#2244
Delete Branch "stop-name-override"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?