Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • erp5 erp5
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Merge requests 142
    • Merge requests 142
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedinexedi
  • erp5erp5
  • Merge requests
  • !1549

Products.ERP5Type.Core.Predicate: asQuery should not force an empty result.

  • Review changes

  • Download
  • Patches
  • Plain diff
Closed Vincent Pelletier requested to merge vpelletier/erp5:predicate_asQuery_return_None into master Feb 04, 2022
  • Overview 19
  • Commits 5
  • Pipelines 0
  • Changes 5

When asQuery is used among more conditions (ex: when publishing documents in a Web Section), the absence of any predicate criterion should not apply any condition on the caller.

This allows the caller to detect the absence of any condition and to take the appropriate decision.

Maintain previous behaviour in callers which did not check a None return value.

/cc @romain @jerome @georgios.dagkakis

Edited Feb 04, 2022 by Vincent Pelletier
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: predicate_asQuery_return_None
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7