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

[Android] Transfer Discovery Detail & Programs Screen to Discovery Module #284

Closed
HamzaIsrar12 opened this issue Apr 4, 2024 · 0 comments · Fixed by #279
Closed

[Android] Transfer Discovery Detail & Programs Screen to Discovery Module #284

HamzaIsrar12 opened this issue Apr 4, 2024 · 0 comments · Fixed by #279
Assignees
Labels
code health Proactive technical investment via refactorings, removals, etc.

Comments

@HamzaIsrar12
Copy link
Contributor

Summary

The Discovery Detail and Programs screens, originally integrated within the Course and Dashboard modules, need to be relocated to the Discovery module. This reassignment aligns with our refined organizational structure, ensuring that related functionality is consolidated under the appropriate module.

Context

Currently, the Discovery Detail and Programs screens are housed within the Course and Dashboard modules. However, to better align with our project's scope and organizational goals, it has been decided to transfer these screens to the Discovery module. This relocation ensures that all discovery-related functionality is centralized, enhancing maintainability and clarity.

Proposed Solution

  • Relocation of Screens: Move the Discovery Detail and Programs screens from their current locations within the Course and Dashboard modules to the Discovery module.
  • Migration of Layers: Migrate the presentation, domain, and data layers associated with these screens to the Discovery module.
  • Transfer of Components: Transfer models, database, repository, and interactions to the Discovery module to ensure seamless functionality.
  • Analytics Integration: Include analytics to provide comprehensive insights and monitoring capabilities during the transition.
@HamzaIsrar12 HamzaIsrar12 added the code health Proactive technical investment via refactorings, removals, etc. label Apr 4, 2024
@HamzaIsrar12 HamzaIsrar12 self-assigned this Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code health Proactive technical investment via refactorings, removals, etc.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant