1. 02 Jul, 2018 1 commit
  2. 22 Jun, 2018 1 commit
  3. 21 Jun, 2018 11 commits
  4. 20 Jun, 2018 2 commits
  5. 19 Jun, 2018 1 commit
  6. 18 Jun, 2018 1 commit
    • Coordinate reachability · f6c56826
      This Merge Request adds ```reachability_workflow``` and adds it to all Coordinate types  (Adress, Email etc.)
      so that the can be marked as ```reachable``` or ```unreachable```.
      It also adds ```coordinate_interaction_workflow```, so that when a coordinate text changes actions can be triggered.
      The default behaviour is that, when coordinate text changes for an 'unreachable' Coordinate, it is marked as reachable.
      
      We already discussed this with @jerome , but I cc @nexedi , since this can break compatibility in projects, because
      in the past Coordinates acquired ```validation_state``` by their parent document (Person, Organisation, etc).
      So now, if some code checks ```getValidationState``` (though it should be checking on the parent) for Coordinate, or searches Catalog with ```validation_state``` (though it should be ```parent_validation_state```), behaviour will change.
      
      Test Result <a href="https://nexedijs.erp5.net/#/test_result_module/20180608-2D68AF16">here</a> seems good (3 failures in UI tests that seem unrelated)
      
      
      /reviewed-on !691
      Georgios Dagkakis committed
  7. 15 Jun, 2018 6 commits
  8. 14 Jun, 2018 13 commits
  9. 13 Jun, 2018 4 commits