1. 03 Jul, 2018 10 commits
    • Vincent Pelletier's avatar
      all: Remove recursiveImmediateReindexObject, and references to it. · 67bb6b90
      Vincent Pelletier authored
      This method does not belong to Folder (nor Base, even as an alias), as
      it recurses wihout any limit in a tree whose node count is unknown.
      Such generic recursion should either be deferred (split in multiple
      transactions, each processing a limited chunk of the tree) or not be
      recursive (which of course depends on the need).
      There is a single caller left (constructInstance) where the subtree size
      is assumed to be reasonable, as it was constructed inside current
      transaction. So essentially rename this method so it is only used in such
      conditions.
      67bb6b90
    • Vincent Pelletier's avatar
      Base: Add isSubtreeIndexable and isAncestryIndexable · 5c4c69a0
      Vincent Pelletier authored
      isAncestryIndexable is a parent-recursive version of isIndexable: it
      will return False if any parent is non-indeable. This simplifies
      disabling indexation of an entire tree, from its root to its deepest
      leaves.
      isSubtreeIndexable allows preventing any subobject from being indexable,
      without having to mark each individual subobject as non-indexable. This
      is different from isAncestryIndexable, as it allows having an indexable
      root, but no children indexable. This is especially useful for Trash Bins,
      where the bin itself should be indexable (because there is no reason not to)
      but its content must not be indexed, while being left as it was found in its
      original location.
      5c4c69a0
    • Vincent Pelletier's avatar
      Folder: Make recursiveReindexObject scalable by calling _recurseCallMethod. · babbf56f
      Vincent Pelletier authored
      Should make Folder_reindexAll and most custom indexation methods obsolete.
      Remaining valid reindexation methods are:
      - reindexObject: for a single document, which may contain subdocuments
        which indexation is not necessary
      - recursiveReindexobject: for any subtree of documents
      - ERP5Site_reindexAll: for site-wide reindexations, as there is a semantic-
        dependent indexation order.
      
      Also, uniformise and factorise spawning immediateReindexObject.
      
      Also:
      - testSupply: Drop check for the previous magic threshold.
        _recurseCallMethod takes care of it all now.
      - testXMLMatrix: Let activities execute before changing cell id.
        This works only because recursiveReindexObject on the matrix spawns a
        single recursiveImmediateReindexObject activity on that context. Now,
        up to 1k immediateReindexObject activities (for the first 1k sub-objects)
        are spawned immediately, preventing their renaming immediately after
        commit.
        So let test wait for indexation before trying to rename.
      - testERP5Security: More activities are now spawned immediately, adapt.
      babbf56f
    • Vincent Pelletier's avatar
      all: Replace after_path_and_method_id on reindexation methods by after_tag · 028c9ad7
      Vincent Pelletier authored
      after_method_id is too aggressive a dependency.
      after_path_and_method_id is marginally better, but is bad practice
      nevertheless, as such activity dependencies remain very hard to introspect.
      Tags allow more variations, and are hence easier to follow.
      Also, add XXX comments when (recursive) reindexation is only added to
      represent the dependency, without certainty that a reindexation is actually
      needed per-se: maybe another place in the code chould just appropriately
      tag its reindexation activities instead, saving at least the cost of
      spawning one more activity set, and at most the cost of actually
      reindexing these documents.
      028c9ad7
    • Vincent Pelletier's avatar
      ERP5Site: Do reindex the whole site after creation. · 9d9e4bbc
      Vincent Pelletier authored
      Also, drop isIndexable instance property, unmasking class property, which
      already has the value we need.
      Also, factorise catalog clearing by reusing ERP5Site_reindexAll's.
      9d9e4bbc
    • Vincent Pelletier's avatar
      CategoryTool: Become a BaseTool subclass. · 4b25512d
      Vincent Pelletier authored
      Allows having a more consistent API between this tool and all other
      Nexedi-maintained tools.
      4b25512d
    • Vincent Pelletier's avatar
      ActivityTool: Inherit from BaseTool. · c3de53b8
      Vincent Pelletier authored
      Reduces code duplication.
      c3de53b8
    • Vincent Pelletier's avatar
      ActivityTool: Do not mark as non-indexable. · c2ebc937
      Vincent Pelletier authored
      portal_activities contains documents which need to be (and are) indexed.
      For consistency, the tool itself should be indexable.
      c2ebc937
    • Vincent Pelletier's avatar
      EPR5Type.Core.Folder: Actually add support for OFS.Folder. · b9202251
      Vincent Pelletier authored
      So it is not just an unused constant (OFS_HANDLER) and no implementation.
      b9202251
    • Vincent Pelletier's avatar
      ERP5Type.Core.Folder: Simplify proxy methods. · 8dcfdf4f
      Vincent Pelletier authored
      Also, clarify what exactly was the broken BTree marker value, fixing
      isBTree accessor. Update associated tests.
      8dcfdf4f
  2. 02 Jul, 2018 3 commits
  3. 29 Jun, 2018 2 commits
  4. 26 Jun, 2018 2 commits
  5. 25 Jun, 2018 1 commit
  6. 22 Jun, 2018 5 commits
  7. 21 Jun, 2018 11 commits
  8. 20 Jun, 2018 2 commits
  9. 19 Jun, 2018 1 commit
  10. 18 Jun, 2018 1 commit
    • Georgios Dagkakis's avatar
      Coordinate reachability · f6c56826
      Georgios Dagkakis authored
      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 nexedi/erp5!691
      f6c56826
  11. 15 Jun, 2018 2 commits