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

Remove HomePageViewController code #3454

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Conversation

dus7
Copy link
Contributor

@dus7 dus7 commented Oct 18, 2024

Task/Issue URL: https://app.asana.com/0/72649045549333/1208547223289954/f
Tech Design URL:
CC: @brindy

Description:

This is a follow up after #3453.

Removes unused code related to HomePageViewController. Home renderers abstraction was also removed, though the implementation itself is used in both Bookmarks controller and to show Favorites while editing URL on non-home tab.

Steps to test this PR:

  1. Make sure code compiles and tests pass.

Definition of Done (Internal Only):

Copy Testing:

  • Use of correct apostrophes in new copy, ie rather than '

Orientation Testing:

  • Portrait
  • Landscape

Device Testing:

  • iPhone SE (1st Gen)
  • iPhone 8
  • iPhone X
  • iPhone 14 Pro
  • iPad

OS Testing:

  • iOS 15
  • iOS 16
  • iOS 17

Theme Testing:

  • Light theme
  • Dark theme

Internal references:

Software Engineering Expectations
Technical Design Template

Copy link

github-actions bot commented Oct 18, 2024

Warnings
⚠️ PR has more than 500 lines of code changing. Consider splitting into smaller PRs if possible.

Generated by 🚫 dangerJS against 0653f8e

Base automatically changed from mariusz/ntp-cleanup to main October 23, 2024 15:31
@dus7 dus7 force-pushed the mariusz/remove-old-home-code branch from 9eb444c to 0653f8e Compare October 25, 2024 08:08
@dus7 dus7 marked this pull request as ready for review October 25, 2024 08:13
@dus7 dus7 requested review from a team and federicocappelli and removed request for a team October 25, 2024 08:43
@federicocappelli
Copy link
Member

Hi @dus7 I have no context about these changes and the task is empty, could you provide some info and testing steps?
I see business logic and UI changes, should the PR contain the steps for testing the involved features?

@@ -169,3 +169,12 @@ struct HomeMessageButtonViewModel {
let action: () async -> Void

}

private extension RemoteAction {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Extracted out of HomeMessageViewSectionRenderer.swift which was deleted.

@@ -83,13 +84,6 @@ class FavoritesHomeViewSectionRenderer: NSObject, HomeViewSectionRenderer {
return Constants.defaultHeaderHeight
}

func install(into controller: HomeViewController) {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one is no longer necessary since there is no HomeViewController.

@@ -43,7 +43,8 @@ class FavoritesHomeViewSectionRenderer: NSObject, HomeViewSectionRenderer {
static let defaultHeaderHeight: CGFloat = 20
static let horizontalMargin: CGFloat = 2
static let largeModeMargin: CGFloat = 24

static let sideInsets: CGFloat = 25
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Extracted from HomeViewSectionRenderers.swift file which was deleted.

@@ -27,21 +27,6 @@ import os.log

final class HomePageConfiguration: HomePageMessagesConfiguration {

enum Component: Equatable {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed since it was used only by HomeViewController which is also removed.

@dus7
Copy link
Contributor Author

dus7 commented Oct 25, 2024

Hi @dus7 I have no context about these changes and the task is empty, could you provide some info and testing steps? I see business logic and UI changes, should the PR contain the steps for testing the involved features?

Hi, I added a few inline comments and an initial PR link in the description. This PR does not cause any UI and/or logic changes. All the modifications were done in previous one (#3453). This is just removing unused code.

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.

2 participants