1. 28 Feb, 2020 5 commits
  2. 27 Feb, 2020 15 commits
  3. 10 Feb, 2020 9 commits
  4. 07 Feb, 2020 2 commits
    • Jérome Perrin's avatar
      ERP5JS: render before commit · dc02bfa8
      Jérome Perrin authored
      Since 264ded5c in ERP5JS we render the form directly after a successful edit, but this was done sometimes too early, namely, the next form was rendered before interaction workflows and this leads to problems like the ones discussed in nexedi/erp5!982 (comment 92893)
      
      /reviewed-on nexedi/erp5!1040
      dc02bfa8
    • Jérome Perrin's avatar
      knowledge_pad_ui_test: fix a random failure · ed44bee5
      Jérome Perrin authored
      This test click on the delete button which deletes by an ajax request
      and immediatly after open the "wait for activities" page. Sometimes the
      second request starts before the first is committed, so there are no
      activities to wait for.
      
      When using ZServer, we had only one worker thread, so this was not
      visible, but with wsgi we have more than one so it happened sometimes.
      
      Use an old jQuery trick to wait that the first request is no longer in
      flight.
      
      /reviewed-on nexedi/erp5!1038
      ed44bee5
  5. 06 Feb, 2020 3 commits
  6. 05 Feb, 2020 3 commits
  7. 04 Feb, 2020 1 commit
  8. 03 Feb, 2020 2 commits
    • Jérome Perrin's avatar
      hal_json_style: after save, render next form later · 97c40dcb
      Jérome Perrin authored
      We want to render the next page after interaction workflows are
      executed.
      97c40dcb
    • Jérome Perrin's avatar
      ui_test: test how interaction workflows can change values when saving · fcde3e85
      Jérome Perrin authored
      This uses a foo_interaction_workflow that sets a short title when title
      is set to a special value. We use it to check that when user set the
      title to that special value and save, next time the form is displayed,
      the values displayed are the ones after interaction workflow modified.
      
      This is a simple and a bit unrealistic scenario, but we have for example
      interaction workflows that update security definitions when some
      properties are modified, we want the next form to display the values
      after modifications.
      
      This is also the case of editions of portal components which sets the
      document to "modified" state and "re-validate" it at the end of
      transaction, unless pylint detects error.
      fcde3e85