Fix/blabsy sidebar

[grv-saini-20]

Description of change

Fixed Blabsy sidebar earlier it is floating to the middle of the small screens now fixed.

Issue Number

closes #742

Type of change

• Update (a change which updates existing functionality)
• Fix (a change which fixes an issue)

How the change has been tested

Manual

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
  • Improved sidebar layout responsiveness across device sizes
  • Updated bottom panel positioning behavior for enhanced layout consistency

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR modifies the sidebar component's responsive Tailwind CSS classes, adjusting the header element's width configuration and converting the bottom panel from fixed to sticky/static positioning across breakpoints to address sidebar centering issues on smaller screens.

Changes

Cohort / File(s)	Summary
Sidebar Layout Fixes platforms/blabsy/src/components/sidebar/sidebar.tsx	Updated header element className with condensed width configuration; converted bottom panel from fixed positioning to fluid sticky/static positioning across xs, md, and xl breakpoints.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• fix:BottomNav-Blabsy-Safari #727: Modifies the same sidebar bottom panel's CSS positioning by adding left-0/right-0 constraints to the fixed positioning setup.

Poem

🐰 The sidebar once wandered left and right,
On tiny screens, a centering blight,
With sticky and static, now tamed just right,
It stays in its place—what a delightful sight! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 16.67% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title "Fix/blabsy sidebar" is directly related to the main change, which fixes the Blabsy sidebar layout issue on small screens.
Description check	✅ Passed	The description includes all major required sections: description of change, issue number, type of change, testing method, and a completed checklist.
Linked Issues check	✅ Passed	The code changes address the sidebar positioning issue on small screens by modifying the responsive layout rules from fixed positioning to static/sticky behavior across breakpoints [#742].
Out of Scope Changes check	✅ Passed	All changes are scoped to the sidebar component styling in sidebar.tsx and directly address the small screen layout issue documented in issue #742.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/blabsy-sidebar

---

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 and usage tips.}

[grv-saini-20]

Please only test the sidebar thing at your machine, lint errors are already resolved in another pr.

[coderabbitai]

Actionable comments posted: 4

🤖 Fix all issues with AI agents

In `@docker-compose.core.yml`:
- Around line 36-74: The neo4j service healthcheck hard-codes the username ("-u
neo4j") so it will fail when NEO4J_USER is overridden; update the neo4j
healthcheck test command in the docker-compose block (healthcheck -> test) to
use the configured environment variable (NEO4J_USER with the same default)
instead of the literal "neo4j" (e.g., use ${NEO4J_USER:-neo4j}) so the
cypher-shell call uses the correct user; keep the existing password substitution
(${NEO4J_PASSWORD:-neo4j}) and the same CMD-SHELL form.
- Around line 76-98: The registry service's environment uses
DATABASE_URL=${REGISTRY_DATABASE_URL} which becomes empty when
REGISTRY_DATABASE_URL is unset; update the registry service (the registry block)
to require REGISTRY_DATABASE_URL at compose parse time by using Docker Compose's
required-variable substitution (make DATABASE_URL reference
REGISTRY_DATABASE_URL with the :? form and include a short error message) so the
stack fails fast with a clear message if REGISTRY_DATABASE_URL is missing.

In `@platforms/blabsy/src/components/sidebar/sidebar.tsx`:
- Around line 75-76: The className string in the Sidebar component (in
components/sidebar/sidebar.tsx) contains a stray double-quote inside the value
(the token `xl:w-72"`), making the Tailwind class invalid; fix it by editing the
className prop (the string containing 'flex shrink-0 w-16 ... xl:w-72"') and
remove the extra `"` so the token becomes `xl:w-72`, ensuring the className
string is a valid quoted string.

In `@platforms/eReputation/client/src/pages/dashboard.tsx`:
- Around line 545-553: The reference badge currently treats any
non-Revoked/Non-Pending status as "signed", which mislabels the new "Unknown"
default; update the JSX that renders the badge (the span inside the
activity.type === 'reference' / activity.activity checks) to explicitly check
for activity.status === 'Unknown' and render a neutral label like "unknown" with
gray/neutral borderBackground/color styles, adjust the conditional that sets the
label (replace the final 'signed' fallback) and the style ternaries to include
activity.status === 'Unknown' so it uses the neutral palette; make the same
change in the mirrored mobile badge block referenced around lines 633-641.

🧹 Nitpick comments (2)

infrastructure/evault-core/src/index.ts (1)

124-127: Make the Fastify body limit configurable via env.

Hard-coding the limit makes environment tuning harder and risks drift vs infra/proxy caps. Consider reading from an env var with a safe default.

♻️ Suggested change

-    fastifyServer = fastify({
-        logger: true,
-        bodyLimit: 20 * 1024 * 1024, // 20MB (default is 1MB; needed for createMetaEnvelope etc.)
-    });
+    const fastifyBodyLimit =
+        Number.parseInt(process.env.FASTIFY_BODY_LIMIT ?? "", 10) ||
+        20 * 1024 * 1024;
+    fastifyServer = fastify({
+        logger: true,
+        bodyLimit: fastifyBodyLimit,
+    });

infrastructure/evault-core/src/test-utils/e2e-setup.ts (1)

123-126: Reuse the same env-based body limit as production to avoid drift.

This keeps E2E behavior aligned with runtime configuration and makes it easier to adjust limits centrally.

♻️ Suggested change

-    const fastifyServer = fastify({
-        logger: false,
-        bodyLimit: 20 * 1024 * 1024, // 20MB, match production limit
-    });
+    const fastifyBodyLimit =
+        Number.parseInt(process.env.FASTIFY_BODY_LIMIT ?? "", 10) ||
+        20 * 1024 * 1024;
+    const fastifyServer = fastify({
+        logger: false,
+        bodyLimit: fastifyBodyLimit, // match production limit
+    });

[coodos]

LGTM now