Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: identify APIs that can be moved to parent component #770

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

paanSinghCoder
Copy link
Contributor

@paanSinghCoder paanSinghCoder commented Sep 9, 2024

Identify API calls which can be potentially moved to top level.

Copy link

vercel bot commented Sep 9, 2024

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

@coveralls
Copy link

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 Coverage Status
Change from base Build 10737736425: 0.0%
Covered Lines: 10679
Relevant Lines: 111643

💛 - Coveralls

@paanSinghCoder paanSinghCoder changed the title chore: identify duplicate API calls chore: identify APIs that can be moved to parent component Sep 9, 2024
@anujk14
Copy link
Contributor

anujk14 commented Oct 16, 2024

@paanSinghCoder Do we still need this? Can we move relevant changes recommended here to a task and close this?

@paanSinghCoder
Copy link
Contributor Author

@anujk14 IMO these are not must have changes thus can be treated as very low priority and can even be discarded.

@anujk14
Copy link
Contributor

anujk14 commented Oct 18, 2024

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants