Skip to content
  1. Mar 31, 2019
  2. Mar 16, 2019
  3. Feb 27, 2019
  4. Feb 24, 2019
  5. Jan 23, 2019
  6. Jan 06, 2019
  7. Dec 21, 2018
  8. Dec 06, 2018
  9. Dec 02, 2018
  10. Nov 30, 2018
  11. Nov 10, 2018
  12. Oct 22, 2018
  13. Oct 11, 2018
  14. Oct 09, 2018
  15. Sep 17, 2018
  16. Sep 16, 2018
  17. Aug 22, 2018
  18. Aug 18, 2018
    • Quentin Defenouillere's avatar
      [bnporc] Included the "Assurance Vie" domain to BNP iter_accounts · 3226d416
      Quentin Defenouillere authored and Romain Bignon's avatar Romain Bignon committed
      The BNP module did not scrape the "Assurance Vie" space yet, which
      may contain additional accounts that are not included in their API.
      Among those we can find Life Insurance, Capitalisation contracts and
      PERP accounts, and maybe more.
      I also implemented the iter_investments() method for this space, however
      the domain does not seem to display any kind of transaction history for
      these accounts.
      
      Closes: 5016@zendesk
      3226d416
    • Nicolas Gattolin's avatar
      [bnporc] py3 port · 5a8411fb
      Nicolas Gattolin authored and Romain Bignon's avatar Romain Bignon committed
      - import unicode_literals in each Python module
      - import weboob's basestring compat
      - xrange -> range
      - tested on 90 connections, 1 for each API
      5a8411fb
  19. Jul 29, 2018
    • Simon Rochwerg's avatar
      [bnporc] handles cases when bnporc's api sends empty json fields for profile · 57e06a10
      Simon Rochwerg authored and Romain Bignon's avatar Romain Bignon committed
      Closes: 9334@sibi
      57e06a10
    • Célande Adrien's avatar
      [bnporc] get rid of bad history for enterprise · f1bcae65
      Célande Adrien authored and Romain Bignon's avatar Romain Bignon committed
      A recurring problem with bnporc is that sometimes you may not have the good transactions list.
      It may be truncated a lot. For example, from 50 transactions, you had only 5.
      Because of that, in the backend some transactions become deleted because of one update with the bad transactions.
      
      I tried to fix it by copying the website, since you never had bad transactions on it.
      First, I changed the 'typeReleve' from 'Comptable' to 'Previsionnel' because it is the only type the website is using.
      And I added some parameters to the history request. The same ones are used to go on the transaction page and to get the json data.
      
      I tested a lot on connections, knowing the right and the wrong history state.
      Since I applied the patch, I had not once the wrong state.
      
      Closes: 5663@zendesk
      Closes: 6219@zendesk
      Closes: 6225@zendesk
      Closes: 6229@zendesk
      Closes: 6115@zendesk
      f1bcae65