Feat/enhance daily interview#892
Conversation
github-actions
Bot
added
gssoc
level:critical
|
Hi @Abfa41, thanks for contributing to InternHack! 🎉 I have automatically:
Our workflows will now analyze your changes to classify:
Tip Ensure your PR description references the issue it resolves (e.g. Happy coding! 🚀 |
|
Warning Review limit reached
More reviews will be available in 9 minutes and 57 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughAdds template seed files and a generator exporting ChangesDaily Interview Tip Widget and Question Bank
Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
@Sachinchaurasiya360 broh, Please review my PR and if any changes are required, do let me know. Please do let me know your Opinion on Focus Mode as well. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (5)
client/src/module/student/applications/questions/interviewTemplates.ts (1)
1-1: ⚡ Quick winRemove unused import.
The
Questiontype is imported but never used in this file. The templates are plain object literals with no type annotations.🧹 Proposed fix
-import type { Question } from "./interviewQuestions"; - export const dsaTemplates = {🤖 Prompt for 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. In `@client/src/module/student/applications/questions/interviewTemplates.ts` at line 1, Remove the unused type import by deleting the import statement "import type { Question } from \"./interviewQuestions\";" from interviewTemplates.ts; the file only contains plain object literals (the template constants) and does not reference the Question type, so removing this import will eliminate the unused import warning.client/src/module/student/applications/questions/interviewQuestions.ts (2)
10-16: ⚡ Quick winConsider narrowing the
categorytype.The
categoryfield is currently typed asstring, but the widget and generation logic use a fixed set of categories:"DSA" | "Frontend" | "Backend" | "System Design" | "HR" | "Behavioral". Using a union type would improve type safety and provide better autocomplete.♻️ Proposed type refinement
+export type QuestionCategory = "DSA" | "Frontend" | "Backend" | "System Design" | "HR" | "Behavioral"; + export interface Question { - category: string; + category: QuestionCategory; difficulty: "Easy" | "Medium" | "Hard"; question: string; answer: string; tips: string[]; }🤖 Prompt for 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. In `@client/src/module/student/applications/questions/interviewQuestions.ts` around lines 10 - 16, The Question interface's category property is too permissive as string; change its type to the explicit union "DSA" | "Frontend" | "Backend" | "System Design" | "HR" | "Behavioral" to improve type safety and autocomplete; update the Question interface declaration (category: ...) in interviewQuestions.ts to that union and adjust any callers or generators that construct Question objects (e.g., functions creating or validating categories) to use the narrowed union values or cast/guard inputs accordingly.
116-116: ⚡ Quick winReplace
anytype with proper template interface.The
templatesparameter is typed asany, which bypasses type checking and hides potential structure mismatches with the imported template objects.♻️ Proposed type definition
Define a template interface at the top of the file:
} from "./interviewTemplates"; +interface QuestionTemplate { + question: string[]; + answer: string[]; + tips: string[][]; +} + export interface Question {Then update the function signature:
function generate( base: Question[], - templates: any, + templates: QuestionTemplate, category: string, target = 30 ): Question[] {🤖 Prompt for 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. In `@client/src/module/student/applications/questions/interviewQuestions.ts` at line 116, Replace the loose any on the templates parameter with a concrete interface describing the expected template structure: add a Templates (or InterviewTemplateMap) interface at the top of the file that defines keys and value shapes used by this module (e.g., title, body, variables, language, etc.), then update the function signature that currently accepts templates: any to use that new Templates type; update any places that construct or pass templates to conform to the interface and adjust call sites/types as needed to satisfy TypeScript checks.client/src/module/student/applications/DailyInterviewTipWidget.tsx (2)
93-100: ⚡ Quick winUse the shared
Buttoncomponent for these new controls.Both the focus toggle and the category filters are new buttons, but they bypass the shared variants/sizes/state handling in
client/src/components/ui/button.tsx. Please compose the motion behavior aroundButtoninstead of introducing raw button styling here. As per coding guidelines, "Use the reusableButtoncomponent fromclient/src/components/ui/button.tsxfor all new buttons; supports variants (primary, secondary, mono, ghost, danger), modes (button, icon, link), and sizes (sm, md, lg)".Also applies to: 135-146
🤖 Prompt for 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. In `@client/src/module/student/applications/DailyInterviewTipWidget.tsx` around lines 93 - 100, The component uses a raw motion.button with inline classes for the focus toggle (and similarly for the category filter buttons at 135-146) which bypasses the shared Button component; replace motion.button with a motion-wrapped shared Button component from client/src/components/ui/button.tsx (e.g., import Button and use motion(Button)) so the controls use the centralized variants/sizes/state handling, preserve the existing tap/hover animations via whileTap/whileHover props on motion(Button), wire onClick to setFocusMode and use the Button variant/size props (choose appropriate variant/size consistent with the app) and ensure the label still reflects focusMode; do the same refactor for the category filter buttons so they all use the shared Button API instead of raw styling.
97-98: ⚡ Quick winReplace the new arbitrary text-size utilities.
These changes add
text-[10px]in several new spots. Please switch to the closest scale token instead of bracket sizing so the widget stays on the canonical Tailwind v4 typography scale. As per coding guidelines, "Do not use arbitrary bracket sizes liketext-[17px], use standard scale classes instead".Also applies to: 117-120, 138-143
🤖 Prompt for 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. In `@client/src/module/student/applications/DailyInterviewTipWidget.tsx` around lines 97 - 98, The component DailyInterviewTipWidget contains arbitrary bracket sizing like text-[10px]; replace those with the closest Tailwind typography token (e.g., text-xs) so the widget follows the canonical scale. Find the className strings in DailyInterviewTipWidget.tsx (the occurrences at the shown diff and the other instances mentioned) and swap text-[10px] for the nearest scale class (suggest text-xs) across all occurrences, keeping the rest of the utility classes unchanged.
🤖 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 `@client/src/module/student/applications/DailyInterviewTipWidget.tsx`:
- Around line 28-32: The component replaced the deterministic daily selection
with Math.random and now randomizes on mount/useEffect and inside handleNav,
causing an initial flash and wrong navigation; restore a date-seeded
deterministic initial index by computing a stable seed-based index synchronously
in the useState initializer for currentIndex (derive seed from the current date
and any category/filter) using filteredQuestions.length, remove the randomizing
useEffect so the component renders the chosen question immediately, and change
handleNav to advance currentIndex by 1 (modulo filteredQuestions.length) rather
than picking a random index; keep the safeIndex/currentIndex logic so q =
filteredQuestions[safeIndex] still works when filters change.
In `@client/src/module/student/applications/questions/interviewQuestions.ts`:
- Around line 96-109: The valuePool object is missing entries for the
{challenge} and {scenario} placeholders used by behavioralTemplates and
hrTemplates; add two new keys (e.g., challenge and scenario) to valuePool with
appropriate string arrays (examples of real challenges and scenarios) so
template substitution works correctly, and ensure the keys match the exact
placeholder names used in behavioralTemplates and hrTemplates.
- Around line 133-138: The variables object currently assigns all placeholders
to the same cycling "value", causing wrong substitutions; update the assignment
so each key uses its own selection from the corresponding pool (e.g.,
conceptPool -> concept, systemPool -> system, skillPool -> skill, situationPool
-> situation) by sampling/advancing indices independently (ensure any index
variables or sampling functions used by createInterviewQuestion or its
surrounding scope are duplicated or separate for concept/system/skill/situation)
and then build const variables: Record<string,string> with those four
independently-chosen values so each placeholder is filled from its correct pool.
---
Nitpick comments:
In `@client/src/module/student/applications/DailyInterviewTipWidget.tsx`:
- Around line 93-100: The component uses a raw motion.button with inline classes
for the focus toggle (and similarly for the category filter buttons at 135-146)
which bypasses the shared Button component; replace motion.button with a
motion-wrapped shared Button component from client/src/components/ui/button.tsx
(e.g., import Button and use motion(Button)) so the controls use the centralized
variants/sizes/state handling, preserve the existing tap/hover animations via
whileTap/whileHover props on motion(Button), wire onClick to setFocusMode and
use the Button variant/size props (choose appropriate variant/size consistent
with the app) and ensure the label still reflects focusMode; do the same
refactor for the category filter buttons so they all use the shared Button API
instead of raw styling.
- Around line 97-98: The component DailyInterviewTipWidget contains arbitrary
bracket sizing like text-[10px]; replace those with the closest Tailwind
typography token (e.g., text-xs) so the widget follows the canonical scale. Find
the className strings in DailyInterviewTipWidget.tsx (the occurrences at the
shown diff and the other instances mentioned) and swap text-[10px] for the
nearest scale class (suggest text-xs) across all occurrences, keeping the rest
of the utility classes unchanged.
In `@client/src/module/student/applications/questions/interviewQuestions.ts`:
- Around line 10-16: The Question interface's category property is too
permissive as string; change its type to the explicit union "DSA" | "Frontend" |
"Backend" | "System Design" | "HR" | "Behavioral" to improve type safety and
autocomplete; update the Question interface declaration (category: ...) in
interviewQuestions.ts to that union and adjust any callers or generators that
construct Question objects (e.g., functions creating or validating categories)
to use the narrowed union values or cast/guard inputs accordingly.
- Line 116: Replace the loose any on the templates parameter with a concrete
interface describing the expected template structure: add a Templates (or
InterviewTemplateMap) interface at the top of the file that defines keys and
value shapes used by this module (e.g., title, body, variables, language, etc.),
then update the function signature that currently accepts templates: any to use
that new Templates type; update any places that construct or pass templates to
conform to the interface and adjust call sites/types as needed to satisfy
TypeScript checks.
In `@client/src/module/student/applications/questions/interviewTemplates.ts`:
- Line 1: Remove the unused type import by deleting the import statement "import
type { Question } from \"./interviewQuestions\";" from interviewTemplates.ts;
the file only contains plain object literals (the template constants) and does
not reference the Question type, so removing this import will eliminate the
unused import warning.
🪄 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: 26b7dc60-821b-4e31-9a0c-eba83ac901a4
📒 Files selected for processing (3)
client/src/module/student/applications/DailyInterviewTipWidget.tsxclient/src/module/student/applications/questions/interviewQuestions.tsclient/src/module/student/applications/questions/interviewTemplates.ts
| const [currentIndex, setCurrentIndex] = useState(() =>0); | ||
| const [focusMode, setFocusMode] = useState(false); | ||
|
|
||
| const safeIndex = currentIndex >= filteredQuestions.length ? 0 : currentIndex; | ||
| const q = filteredQuestions[safeIndex]; |
There was a problem hiding this comment.
Restore date-seeded selection and true next-step navigation.
This replaces the old daily-deterministic flow with Math.random(), so the widget no longer guarantees the same question for everyone on a given day. Because the random pick now happens in useEffect, the component also renders one question first and then immediately swaps to another on mount/category changes. handleNav has the same problem: it randomizes instead of actually moving to the next filtered question.
Suggested direction
+const getDailyIndex = (length: number, seed: string) => {
+ let hash = 0;
+ for (const char of seed) hash = (hash * 31 + char.charCodeAt(0)) >>> 0;
+ return hash % length;
+};
-const [currentIndex, setCurrentIndex] = useState(() =>0);
+const [currentIndex, setCurrentIndex] = useState(() =>
+ getDailyIndex(QUESTIONS.length, `${new Date().toISOString().slice(0, 10)}:All`)
+);
const handleNav = () => {
if (filteredQuestions.length === 0) return;
-
- let next;
-
- do {
- next = Math.floor(Math.random() * filteredQuestions.length);
- } while (next === currentIndex && filteredQuestions.length > 1);
-
- setCurrentIndex(next);
+ setCurrentIndex((prev) => (prev + 1) % filteredQuestions.length);
setExpanded(false);
};
useEffect(() => {
if (filteredQuestions.length === 0) return;
-
- setCurrentIndex(Math.floor(Math.random() * filteredQuestions.length));
+ setCurrentIndex(
+ getDailyIndex(
+ filteredQuestions.length,
+ `${new Date().toISOString().slice(0, 10)}:${categoryFilter}`
+ )
+ );
setExpanded(false);
-}, [categoryFilter]);
+}, [categoryFilter, filteredQuestions.length]);Also applies to: 44-62
🤖 Prompt for 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.
In `@client/src/module/student/applications/DailyInterviewTipWidget.tsx` around
lines 28 - 32, The component replaced the deterministic daily selection with
Math.random and now randomizes on mount/useEffect and inside handleNav, causing
an initial flash and wrong navigation; restore a date-seeded deterministic
initial index by computing a stable seed-based index synchronously in the
useState initializer for currentIndex (derive seed from the current date and any
category/filter) using filteredQuestions.length, remove the randomizing
useEffect so the component renders the chosen question immediately, and change
handleNav to advance currentIndex by 1 (modulo filteredQuestions.length) rather
than picking a random index; keep the safeIndex/currentIndex logic so q =
filteredQuestions[safeIndex] still works when filters change.
Sachinchaurasiya360
left a comment
Sachinchaurasiya360
left a comment
There was a problem hiding this comment.
Code Review — PR #892
The UI improvements (Focus Mode, enhanced animations) are genuinely good additions. However the question generation engine has critical correctness issues that produce broken output, and the overall content quality regresses significantly from the original.
Critical Issues — Unresolved Placeholders
The hrTemplates and behavioralTemplates contain placeholder names that are NOT in the valuePool:
hrTemplates uses {challenge} and {scenario}
behavioralTemplates uses {challenge}
The valuePool only defines: concept, system, skill, situation
These unfilled placeholders will render literally in the widget. A user would see a question reading: What motivates you during {challenge}? or How do you prioritize tasks in {scenario}? This is a broken user experience that ships immediately.
Critical Issue — Semantic Mismatch in Template Engine
All four placeholder types (concept, system, skill, situation) receive the same value:
const variables = {
concept: value,
system: value,
skill: value,
situation: value,
};
The value comes from cycling through the valuePool entries in order. That pool contains: array, stack, queue, graph, React, API (the concept pool), URL shortener, chat system, etc. (system pool), leadership, communication, etc. (skill pool), a tight deadline, a team conflict, etc. (situation pool).
Since all four get the same value, a behavioral template like Describe a situation where you showed {skill} will render as Describe a situation where you showed URL shortener or Tell me about a time you handled array — which is semantically nonsensical. This defeats the purpose of a multi-placeholder template engine.
Significant Quality Regression
The original widget had 15+ full interview-grade questions with 100-200 word answers and specific, actionable tips. The new base seed questions are stubs:
{ question: What is an array?, answer: A linear structure with contiguous memory., tips: [O(1) access, Fixed size] }
These are encyclopedia definitions, not interview answers. A student preparing for interviews needs context, trade-offs, and examples — not one-liners. The generated questions inherit this shallowness and the template answers are equally empty (It improves efficiency by reducing time complexity in operations.).
Code Quality Issues
Type safety: The generate() function signature uses templates: any, bypassing TypeScript type checking entirely. Define a proper interface for the template objects.
Missing EOF newline: Both new files are missing a trailing newline, which triggers linting warnings.
Unused import: interviewTemplates.ts imports type Question from interviewQuestions.ts but does not use it in any exported type.
What to do
Option A (recommended): Keep the UI improvements (Focus Mode, animations) and fix the template engine separately:
- Either restore the original high-quality questions alongside the new ones
- Or fix the placeholder mapping so each template type gets a value from its own semantic pool
- Resolve all unresolved placeholder names before shipping
Option B: Separate the PR into two: (1) UI/animation improvements only (merge-ready), (2) template engine as a follow-up with correct implementation.
Label correction
level:critical is reserved for security vulnerabilities and breaking database changes. This is a UI enhancement — level:intermediate is appropriate. Please request a label update.
Sachinchaurasiya360
added
level:intermediate
github-actions
Bot
added
level:critical
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
client/src/module/student/applications/questions/interviewQuestions.ts (1)
157-157:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winTips are not passed through
fillTemplate.
interviewQuestions.tsassignstips: templates.tips[i % templates.tips.length]directly, so any{concept}/{skill}/{situation}/{challenge}/{system}placeholders present ininterviewTemplates.tswill render unsubstituted.🤖 Prompt for 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. In `@client/src/module/student/applications/questions/interviewQuestions.ts` at line 157, The tips string is assigned directly from templates.tips and so placeholders like {concept}/{skill}/{situation}/{challenge}/{system} remain unsubstituted; change the assignment to pass the selected tip through the same fillTemplate call used for questions (e.g., replace tips: templates.tips[i % templates.tips.length] with tips: fillTemplate(templates.tips[i % templates.tips.length], {concept, skill, situation, challenge, system}) or by passing the same variables/context object used for filling the question in interviewQuestions.ts so tips are rendered correctly.
🧹 Nitpick comments (1)
client/src/module/student/applications/DailyInterviewTipWidget.tsx (1)
93-108: ⚖️ Poor tradeoffUse the shared
Buttoncomponent for new buttons.The Focus Mode toggle, the Next button, and the filter pills (Lines 134-147) are new/changed buttons built from raw
<button>/motion.button. Route them through the reusableButton(e.g.,mode="icon"for the chevron,variant="ghost"/monofor the toggle and filters), usingasChildwhere motion wrapping is needed. The new filter bar also usestext-[10px]; prefer a standard scale class.As per coding guidelines: "Use the reusable
Buttoncomponent fromclient/src/components/ui/button.tsxfor all new buttons" and "Do not use arbitrary bracket sizes liketext-[17px], use standard scale classes instead".🤖 Prompt for 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. In `@client/src/module/student/applications/DailyInterviewTipWidget.tsx` around lines 93 - 108, Replace the raw motion.button and button instances with the shared Button component: wrap the Focus Mode toggle (uses setFocusMode and reads focusMode) with <Button variant="mono" asChild> so you can keep the motion.button for animations, and replace the Chevron Next button (uses handleNav) with <Button mode="icon" variant="ghost">; for the filter pills (the other buttons that toggle filters) use <Button variant="ghost" or variant="mono"> as appropriate. Use asChild when you need to keep motion or custom child elements, and remove arbitrary bracketed sizes (replace text-[10px] with a standard class like text-xs). Ensure the Button props (mode/variant/asChild) match existing Button API and preserve onClick handlers (setFocusMode, handleNav, filter toggles) and accessibility attributes like title.
🤖 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 `@client/src/module/student/applications/questions/interviewQuestions.ts`:
- Around line 123-142: The current pick function uses Math.random() causing
QUESTIONS (built at module load) to be non-deterministic; replace pick with a
deterministic per-pool indexing strategy so the same bank is produced for all
users each day. Implement a stable selector that maintains an index per value
pool (e.g., concept/system/skill/etc.) and picks arr[index % arr.length] while
incrementing or advancing indices in a predictable way (date-seeded or fixed
cycle), and use that selector when building QUESTIONS and when
DailyInterviewTipWidget derives the daily item so the per-day selection is
consistent across users; update references to pick, valuePool, and QUESTIONS
accordingly.
---
Outside diff comments:
In `@client/src/module/student/applications/questions/interviewQuestions.ts`:
- Line 157: The tips string is assigned directly from templates.tips and so
placeholders like {concept}/{skill}/{situation}/{challenge}/{system} remain
unsubstituted; change the assignment to pass the selected tip through the same
fillTemplate call used for questions (e.g., replace tips: templates.tips[i %
templates.tips.length] with tips: fillTemplate(templates.tips[i %
templates.tips.length], {concept, skill, situation, challenge, system}) or by
passing the same variables/context object used for filling the question in
interviewQuestions.ts so tips are rendered correctly.
---
Nitpick comments:
In `@client/src/module/student/applications/DailyInterviewTipWidget.tsx`:
- Around line 93-108: Replace the raw motion.button and button instances with
the shared Button component: wrap the Focus Mode toggle (uses setFocusMode and
reads focusMode) with <Button variant="mono" asChild> so you can keep the
motion.button for animations, and replace the Chevron Next button (uses
handleNav) with <Button mode="icon" variant="ghost">; for the filter pills (the
other buttons that toggle filters) use <Button variant="ghost" or
variant="mono"> as appropriate. Use asChild when you need to keep motion or
custom child elements, and remove arbitrary bracketed sizes (replace text-[10px]
with a standard class like text-xs). Ensure the Button props
(mode/variant/asChild) match existing Button API and preserve onClick handlers
(setFocusMode, handleNav, filter toggles) and accessibility attributes like
title.
🪄 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: f023cd8b-baca-41ac-9462-1d368efbde06
📒 Files selected for processing (3)
client/src/module/student/applications/DailyInterviewTipWidget.tsxclient/src/module/student/applications/questions/interviewQuestions.tsclient/src/module/student/applications/questions/interviewTemplates.ts
💤 Files with no reviewable changes (1)
- client/src/module/student/applications/questions/interviewTemplates.ts
Abfa41
force-pushed
the
feat/enhance-daily-interview
branch
from
5e423a2 to
35c50f4
Compare
|
@Sachinchaurasiya360 broh, I have updated and resolved the changes which you suggested. Just let me know if any changes are required or not. |
Abfa41
added
level:intermediate
2 participants
Description
This PR significantly improves the Daily Interview Tip Widget by upgrading both the UI behavior and the question generation engine.
Major improvements include:
{concept},{system},{skill}, and{situation}{concept}was previously replacedRelated Issue
Fixes #884
Type of Change
Testing
Manually tested the widget in local development:
Verified question generation across all categories
Checked that placeholders are correctly replaced:
{concept}{system}{skill}{situation}Tested category switching and ensured no undefined values appear
Verified random question navigation does not repeat same question consecutively
Confirmed UI renders correctly for all categories
Tested expanded/collapsed answer section behavior
Ensured no runtime errors in console
Creativity / UX Improvements
Focus Mode Feature
A new Focus Mode has been introduced to enhance user concentration during interview practice.
When enabled:
When disabled:
This feature improves usability by allowing users to switch between:
Screenshots
Checklist
.env, credentials, ornode_modulescommittedSummary by CodeRabbit
New Features
Improvements