chore: identify APIs that can be moved to parent component
Identify API calls which can be potentially moved to top level.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| frontier | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Sep 9, 2024 6:58am |
Pull Request Test Coverage Report for Build 10768126423
Details
- 0 of 0 changed or added relevant lines in 0 files are covered.
- No unchanged relevant lines lost coverage.
- Overall coverage remained the same at 9.565%
| Totals | |
|---|---|
| Change from base Build 10737736425: | 0.0% |
| Covered Lines: | 10679 |
| Relevant Lines: | 111643 |
💛 - Coveralls
@paanSinghCoder Do we still need this? Can we move relevant changes recommended here to a task and close this?
@anujk14 IMO these are not must have changes thus can be treated as very low priority and can even be discarded.
@anujk14 IMO these are not must have changes thus can be treated as very low priority and can even be discarded.
@paanSinghCoder Since we had put in effort in identifying these instances, I believe we should add this to a task so that we don't end up spending time again on identifying the same thing again.