It would probably be better to implement something in the visa file
logistics gadget directly, but for now we are still using this. This
used to be a custom capago_rjs_gadget_erp5_pt_form_dialog_* in
capago.git , now we move the patch here.

not sure we'll need this

With this, we accept users with permission to Modify portal content or Associate role

🚧 also fix transition text

With this, change we accept users with permission to Modify portal content or Associate role

This makes this index usable in queries involving flows of movements a resource
on a node at a given date, and still usable for movements of a resource on a
node.

This workflow is used only with portal types translated to french feminine noun (
Campaign, Meeting, Support Request, Software Publication).

XXX but if we consider "${portal_type} à l'état ${state}" then state does not
need to be accordé... maybe this is not a good idea.

Table columns to be displayed by default in the following (from the left to the right of the screen) :

Title
Visa Files Reference
Type
Requester
Begin Date
Comment Date (with possibility to sort the table by this column desc and asc)
Comment Author
State

CUSTOM erp5_officejs_support_request_ui: Change default data to be displayed in support request listboxes

Table columns to be displayed by default in the following (from the left to the right of the screen) :

Title
Visa Files Reference
Type
Requester
Begin Date
Comment Date (with possibility to sort the table by this column desc and asc)
Comment Author
State

HACK: erp5_officejs_support_request_ui: Pass visa file reference as parameter and store as causality

HACK erp5_officejs_support_request_ui: 'Customer Support Dashboard' in 'Support Requests Dashboard' (in header)

In Support request test we trigger clipboard API to copy RSS Link

But, if you running tests manually in your browser, clipboard will fail.
For now, we guarantee that is not break tests on test node

erp5_officejs_support_request_ui: Search action dynamically according to the action category defined on web site

Hard coding to select action_object_view we will never use web site configuration.

If we always get links from action_object_view, Support Request will always break if we change View Action Category on web site.

According to Galien:

In the table, columns to be displayed by default in the following order are :
- Title
- Visa File Reference
- Type
- Requester
- Begin Date
- Comment Date (with possibility to sort the table by this column desc and asc)
- Comment Author
- State

With this, sort by reference will work properly

CUSTOM erp5_officejs_support_request: Add visa_file_reference as parameter and redirect to the expected view

In support request, we need to receive visa_file_reference and store it as causality. With this, we have the relation between Support Request and Visa File

Also, we change the action reference because the previous is not available in our scenario(Default View Action reference).

This will be used by Capago to assign a Support Request to Visa File

Requested in an email from Galien Renault with title "Retour livraison interface consulaire" document "Retour livraison Interface Consulaire ERP5 .pdf". Suppression des boutons d’action : “Sort” / “Edit” / “Select” , section 4.1.4, item a, page 14

Requested in an email from Galien Renault with title "Retour livraison interface consulaire" document "Retour livraison Interface Consulaire ERP5 .pdf" Suppression des boutons d’action : "Sort ", page 4.1.4 item A, page 14

> email from Galien Renault with title "Retour livraison interface consulaire" document "Retour livraison
> Interface Consulaire ERP5 .pdf" Suppression des boutons d’action : ““Edit” / “Select”, page 4.1.4 item a page 14

Requested in an email from Galien Renault with title "Retour livraison
interface consulaire" document "Retour livraison Interface Consulaire
ERP5.pdf", section 4.1.4d page 16

Requested in an email from Galien Renault with title "Retour
livraison interface consulaire" document "Retour livraison Interface
Consulaire ERP5.pdf", part 3.2.2c page 10

- Il devrait être impossible de crée"New Event" pour un
ticket au statut "Closed"

This action is not suppose to work, because they should a new post in the Suppport Request instead of a new event directly.

Because this breaks the sort and filter buttons in the new ERP5 UI

CUSTOM erp5_officejs_support_request_ui: Display causality reference(Visa File Reference) from Support Request

Requested in an email from Galien Renault with title 'Retour livraison interface consulaire' document 'Retour livraison Interface Consulaire ERP5.pdf' V1.0 2020-04-31 section 3.2.1 page 9 and 3.1.9d page 8.

- Rajouter la colonne "Visa Files Reference" en valeur par défaut de l liste 'Recent Update'
- La valeur du champ "Visa File Reference" doit etre la reference TESTVFXXX et non le nom du requester

In this custom support request app, document are sent as items in packing lists
and the default "Attach Document" action is confusing, because we have a
"Create New Document" action which creates the document as an item with its
initial implicit movement.

This script was returning organisations in random order !

When organisation does not have accounting periods, but another organisation at the same level of the same group has, the result was undefined.

This fixes by considering all organisation from the same group.

jerome/erp5!6 rebased and in a big
commit so that we can start using that
SimulationTool: implement "linear" flow API

testInventoryAPI: silent pyflakes warnings

more interpolation implementation

inventory_list interpolation flow: support at_date & to_date

more and more interpolation API

interpolation

interpolation

group_by_time_sequence_list

testInventoryAPI: move inventory valuation methods in a dedicated test class

This should not be in test inventory list.

test: move Tracking API to a dedicated test module

inventory api: dirty way of disabling cache if keys such as node_category are used.

interpolation: security on SimulationTool_zGetInterpolationMethod

SimulationTool_zGetInterpolationMethod is called in restricted context
of Resource_zGetMovementHistoryList so it needs to be usable by
anonymous.

ZSQL Method does not read parameters from REQUEST, so it looks safe.

inventory_api: rely on catalog to add slot_index in the query

instead of implementing this logic in ZSQL's DTML

cf 2c54e0f5

because Domain.getRelativeUrl (and Category.getRelativeUrl) cannot be
restrictedTraverse'd

some work in progress changes to improve developer experience

monaco_editor: increase debounce timeout for pylint checks XXX

on very large python files (>1000 lines) sometimes they queue up and we
have to wait for all requests that were queued by zope.

XXX maybe this does not happen when accessing through haproxy/apache, I
am observing this when hitting zope directly

jedi: generate stubs WIP

ERP5: "quick and dirty" type annotations XXX

IIRC the only thing needed is that ERP5TypeTestCase.getPortal is an
ERP5Site

monaco_editor: also enable jedi for codelens ( WIP: ZMI only )

core: pass "language support url" to text editors XXX

For now this is just the portal_url, but I'm thinking it could be a
proper tool.

monaco_editor: enable pylint in gadget version

because pylint is a bit slow on large components, debounce every 2
seconds. TODO: this is too slow.

monaco_editor: enable formatting provider for python

This makes "Format Document" / "Format Selection" work.

monaco_editor: enable completion provider for python

this makes completions works when using Ctrl+space

monaco_editor: pass portal_type to checkPythonSourceCode

python_support: new business template to act as a language server for python

checkPythonSourceCode: add a cache

When using checkPythonSourceCode integrated in the source code editor,
for a scenario where developer edit a component and save we can benefit
from caching the check message for the source code content, because the
same check that the one happening in the editor will happen when the
component is saved.

This cache varies on:
 - "component_packages" cache cookie which is reset every time some
component code is edited.
 - zope startup time to take into account editions of file system code.
This assumes that after reseting file system code zope will be
restarted.
 - portal_type, because the checks performed by this function also
depend on portal type.

jedi wip

administration: keep using pylint only for now

monaco_editor: jedi WIP

core: use mypy to check python code ( WIP experiment )

Revert "core: use mypy to check python code ( WIP experiment )"

This reverts commit cfa27232.

ERP5TypeTestCase: jedi workarounds

monaco_editor: WIP reference provider for python

monaco_editor: jedi wip (no longer use /tmp/)

yapf: adjust config following up Gabriel feedback

see discussion on !1422 (comment 134105)

See https://zope.readthedocs.io/en/latest/migrations/zope4/zodb.html

The approach here is to have a ZODB patch to apply zodbupdate on object
load, decoding with UTF-8 encoding because it will be correct most of
the time with ERP5