AMM-118: Expose account lock state in SearchEmployee4#123
AMM-118: Expose account lock state in SearchEmployee4#123varundeepsaini wants to merge 1 commit intoPSMRI:mainfrom
Conversation
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, 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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ 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 |
|



Part of PSMRI/AMRIT#118
Description
Extends
m/SearchEmployee4so Employee Master receives account lock state for every row when the list loads.Changes
failedAttempt,lockTimestamp, andlockedDueToFailedAttemptsWhy this shape was required
SearchEmployee4