Fix/evoting alignment

[Sahil2004]

Description of change

Fixed the alignment issue in evoting app.

Desktop:

Mobile:

Issue Number

Closes #1051
Closes #1060

Type of change

• Fix (a change which fixes an issue)

How the change has been tested

Manually.

Change checklist

• I have ensured that the CI Checks pass locally
• I have removed any unnecessary logic
• My code is well documented
• I have signed my commits
• My code follows the pattern of the application
• I have self reviewed my code

Summary by CodeRabbit

• Style

  • Adjusted the poll creation screen layout so the “Add Option” and “Cancel” controls display more cleanly on different screen sizes.

• Chores

  • Updated the example environment settings with a new default voting service URL for easier local setup.

[coderabbitai]

Warning

Review limit reached

@Sahil2004, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 6 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 25b463d9-78c8-4cb8-a1a4-59ac348e0e5e

📥 Commits

Reviewing files that changed from the base of the PR and between 3ae7f54 and f73bc2d.

📒 Files selected for processing (1)

• platforms/evoting/client/src/app/(app)/create/page.tsx

📝 Walkthrough

Walkthrough

This PR updates the eVoting client's example environment file to set a new base URL, and adjusts CSS class structure for the "Add Option" and "Cancel" buttons on the create vote page to fix alignment inconsistencies.

Changes

eVoting Create Vote UI Fix

Layer / File(s)	Summary
Create vote button alignment fixes platforms/evoting/client/src/app/(app)/create/page.tsx	"Add Option" button container simplified to mt-3 block; "Cancel" Link gets flex-1 and its Button gets w-full for consistent alignment.
Example env base URL update platforms/evoting/client/example.env	NEXT_PUBLIC_EVOTING_BASE_URL updated to http://192.168.0.235:7777.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Possibly related issues

• eVoting: "Add Option" & "Cancel" buttons have poor UX in poll creation #1060: The poll creation form button layout tweaks in create/page.tsx directly address the same "Add Option" and "Cancel" alignment issue.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Out of Scope Changes check	⚠️ Warning	The example.env base URL update is unrelated to the Create Vote alignment fix.	Remove the example.env URL change unless it is required for the alignment fix and explain that dependency in the description.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	The UI layout updates in create/page.tsx address the reported Add Option and Cancel button misalignment.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title is concise and accurately reflects the UI alignment fix in the eVoting flow.
Description check	✅ Passed	The description matches the template with change summary, issue number, type, testing, and checklist.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/evotingAlignment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@platforms/evoting/client/src/app/`(app)/create/page.tsx:
- Around line 679-682: Avoid nesting the Button component inside Link in the
create page action area, since it creates an anchor wrapping a button and can
lead to inconsistent interaction behavior. Update the existing Link/Button
pairing in the create page so that Button uses asChild with Link as the child,
or remove Button entirely and apply the same styling directly to Link. Use the
Link and Button JSX in the current create page section to locate and adjust this
pattern.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c7f6a74c-4b52-46c3-8cd5-0fccef010498

📥 Commits

Reviewing files that changed from the base of the PR and between 388ccb2 and 3ae7f54.

📒 Files selected for processing (2)

• platforms/evoting/client/example.env
• platforms/evoting/client/src/app/(app)/create/page.tsx