Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • erp5 erp5
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Merge requests 141
    • Merge requests 141
  • 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
  • nexedi
  • erp5erp5
  • Merge requests
  • !334

Merged
Created Jul 27, 2017 by Tomáš Peterka@katomasoContributor

Hotfix/test listbox order

  • Overview 0
  • Commits 4
  • Changes 10

ListBox "sort" field which describes default sort is implemented using ListTextAreaField. As you can see it replaces single value "V" with "V | V". This works for sort/search columns definition because they expect "column-name | title".

ERP5 (SelectionTool) is benevolent and gracefully omits such meaningless sort expression as "id | id" and sorts ASC by default.

Old UI is very nice to the implementator and shows sort as ascending in case it is not descending. Which is true but leaves the implementator to get lazy with definitions.

New UI refuses to show any sort which is not properly defined. Thus sort values in ERP5 has to be defined as "<column> | <order>". Examples: "id | ASC", "title | DESC".

Test Result https://nexedijs.erp5.net/#/test_result_module/20170727-1803130F

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: hotfix/test-listbox-order
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7