1. 14 Apr, 2022 4 commits
    • Jérome Perrin's avatar
      *: re-export components without the error_message workflow variable · f1a814e2
      Jérome Perrin authored
      follow up of 8a335cca (component: fix error_message saved in every line of history, 2022-02-18)
      f1a814e2
    • Jérome Perrin's avatar
      CodingStyle: verify that business template re-exporting is stable · 7fd94178
      Jérome Perrin authored
      re-exporting a business template that was just installed should not be
      different.
      
      By having a test reporting diffs in export, we can detect changes in ERP5 or
      dependencies which would cause the business template format to become different.
      The primary reason for doing this was to make sure that on the way to Zope4 we
      don't have changes in exported data, especially lossly changes that would not
      be detected in test suite, but this is also good because it helps detecting
      changes that cause a difference in output - then if we introduce a change that
      cause different business template export, we also have to make a change to
      re-export everything to new format, which helps keeping the git history cleaner
      because there's one big commit with all the changes instead of having many small
      commits. This is also good because it detects mistakes when modifying business
      templates files directly with a text editor.
      
      The test can be configured to ignore some paths, using fnmatch pattern (which
      unlike business patterns do not support ** for recursive match). This is also
      helpful when using this test case to check customer configuration business
      templates, where we may want to ignore some PathTemplateItem for conveniance.
      
      This also include fix for almost all current cases where re-exporting produce
      a diff, except a few cases that the reason for the diff was not understood, they
      were added to the ignore list instead.
      
      
      See merge request !1575
      7fd94178
    • Jérome Perrin's avatar
      Formulator,xhtml_style: render multi radio and checkboxs with a label · 4086f9a6
      Jérome Perrin authored
      This way, clicking on the label is enough to select the radio button,
      or tick the checkbox, no need to click on the small button.
      This is also probably better for accessibility.
      
      CSS is adjusted a bit, so that the style for "general" field labels
      do not apply to this new label.
      4086f9a6
    • Jérome Perrin's avatar
      *_ui_test: make Zelenium tests compatible with Zope4 ZMI · 87c30a04
      Jérome Perrin authored
      The status message no longer use system-msg class, use simpler
      "assertTextPresent" that should be enough.
      
      Simplify the waiting for static pages, clickAndWait is enough.
      87c30a04
  2. 12 Apr, 2022 1 commit
  3. 11 Apr, 2022 1 commit
  4. 08 Apr, 2022 3 commits
  5. 07 Apr, 2022 2 commits
  6. 05 Apr, 2022 8 commits
  7. 31 Mar, 2022 5 commits
  8. 30 Mar, 2022 1 commit
  9. 29 Mar, 2022 1 commit
  10. 24 Mar, 2022 2 commits
    • Julien Muchembled's avatar
      ERP55Form: drop a broken proxy field cache · 25ad9ece
      Julien Muchembled authored
      When rendering a proxy field, 3 different fields can come in play:
      1. the field to be rendered
      3. the template field (i.e. not a proxy field) that knows how to render
      2. possibly an intermediate proxy field that contains the value to render
      
      What's difficult when rendering a proxy field is to take the above 3 fields
      into account and this commit does it by creating a temporary field:
      1. 'field' variable in TALES
      2. the value
      3. the code
      
      Before this commit, 1 could be wrong.
      25ad9ece
    • Jérome Perrin's avatar
      *: stop using deprecated getWorkflowById · cc60f03a
      Jérome Perrin authored
      This was deprectated because we don't have get*ById for other modules
      and tools, we just use OFS API. This should also be slightly faster
      because one less method call (and one less call to warning)
      cc60f03a
  11. 23 Mar, 2022 4 commits
  12. 22 Mar, 2022 1 commit
  13. 21 Mar, 2022 2 commits
  14. 18 Mar, 2022 1 commit
    • Jérome Perrin's avatar
      web_renderjs_ui,officejs: don't use zope's favicon.ico · 03674992
      Jérome Perrin authored
      Most service worker precache scripts reference a favicon.ico, but this
      is using the default favicon.ico from Zope and even though it was included
      in all ERP5JS and OfficeJS web sites, this was mostly not used, only
      web_renderjs_ui web pages reference favicon.ico.
      
      There's a favicon.ico in erp5_xhtml_style skin folder, but the skin
      folder is not in ERP5JS skin selection.
      
      On Zope2, this caused ERP5JS and OfficeJS application use the default
      Zope favicon. On Zope4, the service worker can not fill its cache
      because of 404 errors, because since Zope commit 4f0770941 (Retired
      icons from the `Zope Management Interface` and various smaller cleanups
      of ZMI screens., 2011-07-02) there's no default favicon.ico anymore.
      
      To solve this, provide a favicon.ico in ERP5JS skin selection, by
      copying the one from erp5_xhtml_style. We also reference it explicitly in
      web site layout properties so that it remain in the cache.
      
      OfficeJS applications do not use favicon.ico explicitly. They use icons
      in their web application manifest, but this does not seem to be use as
      favicon unless the PWA is installed. This part is not addressed by this
      commit.
      03674992
  15. 17 Mar, 2022 4 commits
    • Jérome Perrin's avatar
      c1f288b3
    • Jérome Perrin's avatar
      01d73a50
    • Jérome Perrin's avatar
      Workflow: add a simple _checkConsistency implementation · d1be5248
      Jérome Perrin authored
      For now only checks that error_message is missing, but later we might
      extended this to perform more check on the workflow definition.
      d1be5248
    • Jérome Perrin's avatar
      core_test: increase expected value testWorkflowHistoryList.TestDedup · 0eca529a
      Jérome Perrin authored
      After df85ef46 (ERP5Workflow: DC Workflows are now ERP5 objects (!1378).,
      2020-11-18) we increased the expected value from 24 to 36, because it
      was just different with new workflow implementation and what was important
      is to have large buckets.
      
      After that, the test was flaky and eventually we changed the assertion
      from checking that the value equal the expected value to checking that
      it's larger to checking that it's larger to a satisfying value and we
      used the initial 24 for satisfying value.
      
      A large value here means the bucket contain many items, which happens
      when the pickle size is small
      
      We now understand that pickle are short when the pickler was able to
      deduplicate some strings because they were the same instances (as
      compared by `is` operator). Note that this deduplication happens before
      the one operated by Products.ERP5Type.Workflow.dedupStrings after bucket
      rotation, it's the "normal" deduplication from pickle happening when
      element are added to list.
      
      Because it's a good thing for disk usage to have small pickles, we raise
      our expectation and increase the expected minimal value to be 30.
      0eca529a