[Frontend] Duplicated duration-unit-to-seconds constants (ScheduleStep vs lib/soroban)

[ogazboiz]

Telegram: https://t.me/+DOylgFv1jyJlNzM0

Why this matters

The seconds-per-unit mapping for stream durations is defined twice with magic numbers:

• frontend/src/lib/soroban.ts — SECONDS_PER_UNIT (BigInt: minutes 60, hours 3600, days 86400, weeks 604800, months 2592000)
• frontend/src/components/stream-creation/ScheduleStep.tsx — an inline switch repeating the same * 60 / * 3600 / * 86400 / * 604800 / * 2592000 literals

If one is changed (e.g. "months" definition), the preview rate in the wizard and the actual submitted duration can silently diverge.

Acceptance criteria

• Export a single shared seconds-per-unit map (or a toDurationSeconds-style helper) and use it in both places
• Wizard rate preview and submitted duration stay consistent

Files to touch

• frontend/src/lib/soroban.ts
• frontend/src/components/stream-creation/ScheduleStep.tsx

Out of scope

• Other amount helpers.

[Johnjnr1]

@Johnjnr1 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi, I'd like to work on this issue! because I am very conversant with solving problems like this!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Johnjnr1 to this issue.

[SharifIbrahimDev]

@SharifIbrahimDev has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi @ogazboiz, I’d like to work on this issue.

I can refactor the duplicated duration conversion logic into a single shared utility to ensure the stream preview calculations and submitted durations always remain consistent.

My implementation will include:

• Extracting a shared SECONDS_PER_UNIT map or reusable duration conversion helper
• Updating both soroban.ts and ScheduleStep.tsx to use the shared source of truth
• Removing duplicated magic numbers and inline conversion logic
• Verifying that wizard rate previews and submitted stream durations remain fully aligned

I’ll also ensure the refactor is type-safe, maintainable, and introduces no behavioral changes outside the intended consistency improvement.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @SharifIbrahimDev to this issue.

[drips-wave]

Congratulations, @SharifIbrahimDev! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @SharifIbrahimDev: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @SharifIbrahimDev as part of the Stellar Wave Program's 5th Wave 🥳

😎 @SharifIbrahimDev: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.