Skip to content
This repository has been archived by the owner on Nov 5, 2024. It is now read-only.

Technical Debt : Migrate the code to use the new the CategoryRepository #3583

Merged
merged 4 commits into from
Oct 4, 2024

Conversation

priyatanu
Copy link
Contributor

@priyatanu priyatanu commented Oct 4, 2024

Pull request (PR) checklist

Please check if your pull request fulfills the following requirements:

  • I've read the Contribution Guidelines and my PR doesn't break the rules.
  • I've read and understand the Developer Guidelines.
  • I confirm that I've run the code locally and everything works as expected.
  • My PR includes only the necessary changes to fix the issue (i.e., no unnecessary files or lines of code are changed).
  • 🎬 I've attached a screen recording of using the new code to the next paragraph (if applicable).

Screen recording of your changes (if applicable):

Uploading Screen_recording_20241004_191914.webm…

What's changed?

Describe with a few bullets what's new:

  • I've fixed migrated to use the new the CategoryRepository and remove usages with CategoryDao &WriteCategoryDao

Risk factors

What may go wrong if we merge your PR?

  • Back Up data may go wrong

In what cases won't your code work?

  • N/A

Does this PR close any GitHub issues? (do not delete)

Troubleshooting GitHub Actions (CI) failures ❌

Pull request checks failing? Read our CI Troubleshooting guide.

@ILIYANGERMANOV ILIYANGERMANOV merged commit 5c532c9 into Ivy-Apps:main Oct 4, 2024
17 of 18 checks passed
@priyatanu priyatanu deleted the fix-issue-2962 branch October 5, 2024 08:35
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Data Layer] Migrate the code to use the new the CategoryRepository
2 participants