Change Details

More details to be added, likely still using form elements but then using .serialise() jquery functions to convert it to postable JSON This means we don't need to reload the page, which is better for UX and allows us to keep the current client side image loaded without fancy extra code to redirect back to the last image they worked on. **Data to post as JSON string:** e.g. When Nigeria has been selected as Wiki Loves country on "Person playing chess" image: [ {"image", "Person playing chess", "edit_type": "depicts", "edit_action": "add", "edit_content": "Q5", "country": "Nigeria"}, {"image", "Person playing chess", "edit_type": "depicts", "edit_action": "remove", "edit_content": "Q27", "country": "Nigeria"}, ] Or, no Wiki Loves country selected: [ {"image", "Person playing chess", "edit_type": "depicts", "edit_action": "add", "edit_content": "Q5"}, {"image", "Person playing chess", "edit_type": "depicts", "edit_action": "remove", "edit_content": "Q27"}, ] A caption example: [ {"image", "Person playing chess", "edit_type": "caption", "edit_action": "add", "edit_content": "{language: "en", "A person playing a game of chess}"}, ]

This means we don't need to reload the page, which is better for UX and allows us to keep the current client side image loaded without extra code to redirect back to the last image they worked on. Data is posted as a JSON string using new API route ( api/post-contribution). This has been tested locally but the actual route on the server has been left out of this commit to avoid merge conflicts (this will be added in {T224968} - Add postContribution(editType) method to Participation manager, which sends JSON string to server for depicts or captions - Setup cancel and publish buttons for depicts and captions - Added new functions to reset to initial state (for cancel buttons) - Update stored initial data and button states after contribution is sent - Create functions to get current depicts/captions data as shown in the UI (needed now this logic is used in more than one place)

More details to be added, likely still using form elements but then using .serialise() jquery functions to convert it to postable JSON This means we don't need to reload the page, which is better for UX and allows us to keep the current client side image loaded without fancy extra code to redirect back to the last image they worked on. **Data to post as JSON string:** e.g. When Nigeria has been selected as Wiki Loves country on "Person playing chess" image: [ {"image", "Person playing chess", "edit_type": "depicts", "edit_action": "add", "edit_content": "Q5", "country": "Nigeria"}, {"image", "Person playing chess", "edit_type": "depicts", "edit_action": "remove", "edit_content": "Q27",Data is posted as a JSON string using new API route ( api/post-contribution). "country": "Nigeria"}, ]This has been tested locally but the actual route on the server has been left out of this commit to avoid merge conflicts (this will be added in {T224968} Or, no Wiki Loves country selected: [ {"image", "Person playing chess", "- Add postContribution(edit_type": "depicts", "edit_acType) method to Participation": "add" manager, "edit_content": "Q5"},which sends JSON string to server for depicts or captions {"image", "Person playing chess", "edit_type": "depicts", "edit_action": "remove", "edit_content": "Q27"}, ] A- Setup cancel and publish buttons for depicts and caption example:s [- Added new functions to reset to initial state (for cancel buttons) {"image", "Person playing chess", "edit_type": "caption", "edit_action": "add", "edit_content": "{language: "en", "A person playing a game of chess}"},- Update stored initial data and button states after contribution is sent ]- Create functions to get current depicts/captions data as shown in the UI (needed now this logic is used in more than one place)