Skip to content
  1. Feb 24, 2019
  2. Feb 05, 2019
  3. Jan 23, 2019
    • Quentin Defenouillere's avatar
      [cragr] Implemented navigation for new Cragr website · 5cf9b644
      Quentin Defenouillere authored and Romain Bignon's avatar Romain Bignon committed
      Crédit Agricole now uses an API.
      This commit enables site switching for the connections of the new
      website and keeps the former behavior for the connections that still use
      the previous website.
      This commit was tested with the backend and we observed no duplicated
      account since all the account IDs correctly match the former website
      behavior.
      All other methods than iter_accounts() return BrowserUnavailable for
      now.
      
      Closes: 9101@zendesk
      5cf9b644
    • Martin Sicot's avatar
      [cragr] Fix crash due to missing balance · 42475507
      Martin Sicot authored and Romain Bignon's avatar Romain Bignon committed
      On this quality website the balance of one life insurance was missing
      and was not retrievable in any way on the website itself. It caused a
      crash because we expected to land on the BGPIPage. We now do not try to
      retrieve missing balance if we are not already on a BGPIPage.
      
      closes: 8688@zendesk
      closes: 8846@zendesk
      closes: 8359@zendesk
      closes: 30787@sibi
      42475507
    • ntome's avatar
      [cragr] 'warn' exists for Logger, not LoggerAdapter · 8449be91
      ntome authored and Romain Bignon's avatar Romain Bignon committed
      8449be91
  4. Jan 13, 2019
    • Martin Sicot's avatar
      [cragr] date_guesser modified · cfbdde18
      Martin Sicot authored and Romain Bignon's avatar Romain Bignon committed
      Transactions DO NOT have a year. its only DD/MM. In some cases, if there
      aren't enough
      transactions in the account, a transaction dating from last year has its
      date incorrectly
      guessed (with the date_guesser/ to avoid this we had to reduce
      data_guesser.date_max_bump
      to 2 in order to prevent such problems, but only for savings accounts.It
      is not perfect,
      hence the assertion to make sure we aren't returning a future date that
      is more than 2 days forward.
      
      At date "2018/12/03", the site only shows one transaction with date
      "29/12", so this interpreted as "2018/12/29" (future) instead of
      "2017/12/29" (past).
      If there were more transactions in the year, this wouldn't happen
      cfbdde18
  5. Jan 06, 2019
  6. Dec 21, 2018
  7. Dec 17, 2018