It is easy to cause problems when multiple UIScrollViews are mixed. Nesting of ScrollView (and its subclasses) is not recommended. You can use tableView.headerView and Section.headerView to achieve the required functions
Static tableView is generally used for relatively simple layouts. Not recommended. Just use code. You can customize a cell and add a tableView. But this is generally not required. It is not recommended to write like this. If you are imagining the expansion function of the address book. You can use tableHeaderView to write.
It is easy to cause problems when multiple UIScrollViews are mixed. Nesting of ScrollView (and its subclasses) is not recommended. You can use tableView.headerView and Section.headerView to achieve the required functions
Yes, just like you usually put a view in the cell, and then write the proxy in the inserted tableView file
Static tableView is generally used for relatively simple layouts. Not recommended. Just use code. You can customize a cell and add a tableView. But this is generally not required. It is not recommended to write like this. If you are imagining the expansion function of the address book. You can use tableHeaderView to write.
If you want to avoid pitfalls, it would be much better to seal the tableView and the tableView in the cell and write them separately