Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
erp5 erp5
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 141
    • Merge requests 141
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • erp5erp5
  • Merge requests
  • !1549

Closed
Created Feb 04, 2022 by Vincent Pelletier@vpelletierOwner
  • Report abuse
Report abuse

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

  • Overview 19
  • Commits 5
  • 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
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: predicate_asQuery_return_None
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7