there is a requirement to ask you whether there is a good way to design and implement?
after the administrator logs in to the background, you can enter the article management module;
- the
< select/ >form component should be included in the article list. You can choose our own vest user ; .
- whenever you choose a waistcoat , such as waistcoat a , the article list should be updated, because every article in the article list will have the status of whether the vest has been liked or not. Click an article in the
- article list to enter the article details page. In the details page, the form components of
< select/ >can also select vest user (the default is vest a selected in the list page); - if you select waistcoat b on the details page, return to the article list after performing the operation in the details page, and the
< select/ >form component in the article list should also be updated to vest b (list page to be updated, step 2 has been explained)
the actual situation is that the background of the API for obtaining the vest list is paged, and the article list is also paged. (and there is a special module for managing vest users, which can be edited in the vest list page to add vest users)
is there any good way to solve this problem?