David Rodríguez 915d03a66a Change CreditCardRemover specs to not send raw credit card data
If I re-record cassettes for these specs using my test API key, I get
the following errors:

```
1) Stripe::CreditCardRemover#remove Stripe customer exists and is not deleted deletes the credit card clone and the customer
   Failure/Error:
     Stripe::PaymentMethod.create(
       {
         type: 'card',
         card: {
           number: '4242424242424242',
           exp_month: 8,
           exp_year: Time.zone.now.year.next,
           cvc: '314',
         },
       },

   Stripe::CardError:
     Sending credit card numbers directly to the Stripe API is generally unsafe. We suggest you use test tokens that map to the test card you are using, see https://stripe.com/docs/testing. To enable testing raw card data APIs, see https://support.stripe.com/questions/enabling-access-to-raw-card-data-apis.
   # ./spec/lib/stripe/credit_card_remover_spec.rb:16:in `block (3 levels) in <main>'
   # ./spec/lib/stripe/credit_card_remover_spec.rb:44:in `block (4 levels) in <main>'
   # ./spec/lib/stripe/credit_card_remover_spec.rb:56:in `block (4 levels) in <main>'
   # ./spec/base_spec_helper.rb:208:in `block (2 levels) in <main>'
   # ./spec/base_spec_helper.rb:155:in `block (3 levels) in <main>'
   # ./spec/base_spec_helper.rb:155:in `block (2 levels) in <main>'
   # -e:1:in `<main>'
```

Use test payment methods instead as suggested by the error.
2025-11-06 18:30:45 +01:00
2025-10-29 11:55:10 +01:00
2022-11-04 09:46:11 +11:00
2022-09-21 12:21:49 +10:00
2025-10-27 11:30:33 +01:00
2025-10-10 16:18:22 +11:00
2025-10-10 16:18:22 +11:00
2022-10-10 16:09:43 +02:00
2024-10-08 13:26:57 +11:00
2025-10-21 15:56:50 +11:00
2024-10-14 15:01:18 +11:00
2024-05-08 13:31:35 +10:00
2025-10-27 11:30:33 +01:00
2025-10-31 15:30:17 +11:00
2025-10-27 11:30:33 +01:00
2025-10-31 09:18:11 +01:00
2022-10-12 09:28:50 +02:00
2023-04-26 09:44:58 +10:00
2025-10-31 09:18:11 +01:00
2021-06-19 17:51:18 +01:00
2025-03-18 03:35:45 +05:00
2024-02-23 11:28:18 +00:00
2025-11-03 05:17:35 +00:00

Build

Open Food Network

The Open Food Network is an online marketplace for local food. It enables a network of independent online food stores that connects farmers and food hubs (including co-ops, online farmers markets, independent food businesses, etc) with individuals and local businesses. It gives farmers and food hubs an easier and fairer way to distribute their food.

Supported by the Open Food Foundation and a network of global affiliates, we are proudly open source and not-for-profit - we're trying to seriously disrupt the concentration of power in global agri-food systems, and we need as many smart people working together on this as possible.

We're part of global movement - get involved!

  • Join the conversation on Slack. Make sure you introduce yourself in the #general channel and join #dev for all tech-related topics.
  • Head to https://openfoodnetwork.org for more information about the global OFN project.
  • Check out the User Guide for a list of features and tutorials.
  • Join our discussion forum.

Contributing

If you are interested in contributing to the OFN in any capacity, please introduce yourself on Slack, and have a look through the OFN Handbook.

Our GETTING_STARTED and CONTRIBUTING guides are the best place to start for developers looking to set up a development environment and make contributions to the codebase.

Hacktoberfest 🎉

Are you participating in Hacktoberfest? Go check out our Welcome New Developers project board! We have curated all issues we consider to be a good starting point for new members of the community and categorized them by skills and level of complexity. Have a look and pick the one you would prefer working on!

Provisioning

If you're interested in provisioning a server, see ofn-install for the project's Ansible playbooks.

We also have a Super Admin Guide to help with configuration of new servers.

Testing

If you'd like to help out with testing, please introduce yourself on the #testing channel on Slack. Also, do have a look in our Welcome New QAs board for some good first issues, both on manual and automated testing (RSpec/Capybara).

We use BrowserStack as a manual testing tool. BrowserStack provides open source projects with unlimited and free of charge accounts. A big thanks to them!

We use KnapsackPro for optimal parallelisation of our automated tests. KnapsackPro offers unlimited plans for non-commercial open source projects, like ours - a big thanks to them!

image

Licence

Copyright (c) 2012 - 2024 Open Food Foundation, released under the AGPL licence.

Description
Connect suppliers, distributors and consumers to trade local produce.
Readme 157 MiB
Languages
Ruby 74.7%
Haml 9.4%
CoffeeScript 7.3%
SCSS 4.5%
JavaScript 3.6%
Other 0.4%