A high-performance JavaScript 2D/3D polyline simplification library
A WGS84 geography feature simplifier, based on simplify-js
A WGS84 geography feature simplifier, based on simplify-js
Simplify JS objects, replacing circular references by the path leading to the parent reference. Useful before a JSON.stringify() or a recursive navigation over the object.
Simplify a 2d point-map with Simplify-js
A better Object.defineProperty()
Reduces the number of points in a shape while keeping its overall look.
Validation, extraction and creation of IBAN, BBAN, BIC/SWIFT numbers plus some other helpful stuff like ISO 3136-1 alpha 2 country list
Apply Ramer-Douglas-Peucker line simplification to GeoJSON features or feature collections in JS or on the CLI
Topology-preserving simplification and filtering for TopoJSON.
Convert === and !== to == and != if their types are inferred to be the same.
Library to simplify JS tasks.
A fork of simplify-js for JavaScript 2D/3D polyline simplification library
> Simplifies code for minification by reducing statements into expressions and making expressions uniform where possible.
Simplify geometry using the Ramer–Douglas–Peucker algorithm.
simplify 2D polyline
Delightful JavaScript Testing.
Delightful JavaScript Testing.
Adds a static `extend` method to a class, to simplify inheritance. Extends the static properties, prototype properties, and descriptors from a `Parent` constructor onto `Child` constructors.
🐊Putout plugin adds ability to simplify ternary operator
Symbolic computing and numeric evaluations for JavaScript and Node.js
TypeScript definitions for topojson-simplify
Simplifies a planar graph
An Angular testing library for creating mock services, components, directives, pipes and modules in unit tests. It provides shallow rendering, precise stubs to fake child dependencies. ng-mocks works with Angular 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Simplify polylines using Douglas-Peucker and radial distance algorithms. Port of the simplify-js library.
simplify-js port to rust
A cross-platform Pact verification tool to validate API Providers. Used in the pact-js-provider project to simplify development
A cross-platform Pact verification tool to validate API Providers. Used in the pact-js-provider project to simplify development
Small gem to simplify building process of gems with git submodules. Tended to be used for ruby gems which wrap js libraries or another assets
Edifice makes your Rails life easier. It's designed to simplify CSS & JS integration in your Rails app by following the principle of DRY, less obtrusive markup. Stop writing unnecessary javascript boilerplate, stop wasting time namespacing view CSS and start enjoying rails again..
haml_to_js is a ruby library and command line that converts haml to javascript. Why an other haml to js converter (see similar utilities) ? It is a extension of [haml_to_star](https://github.com/sdrdis/haml_to_star) which purpose is to convert haml into any language. This converter is intended for front usage. It simplifies debugging (the generated code is readable, a variable hold haml line number so you can know exactly where the problem is).
# Payfast Payfast is a Ruby gem that simplifies the process of integrating the PayFast payment gateway into your Ruby on Rails application. It provides a generator that helps scaffold the necessary configuration, routes, models, and controllers required to integrate PayFast seamlessly. ## Demo  ## Installation Add this line to your application's Gemfile: ```bash bundle add payfast ``` ## Usage ```bash rails generate payfast:install ``` ## This generator will perform the following actions: insert config/routes.rb create app/controllers/carts_controller.rb create app/views/carts/index.html.erb create app/views/carts/make_payment.html.erb create app/helpers/carts_helper.rb create db/migrate/20230824105530_create_carts.rb create config/payfast.yml create app/models/cart.rb insert app/views/layouts/application.html.erb insert config/environments/development.rb ## Additional configuration Setup payfast credentials for your environment rails EDITOR="code --wait" bin/rails credentials:edit This will allow you to securely edit and store your credentials. once you save and exit the file, the credentials will be encrypted and can only be accessed withe rails master key. payfast: merchant_id: {your_merchant_id} merchant_key: {your_merchant_key} passphrase: {{your_passphrase}} ## Update your `payfast.yml` config file - setup the credentials to be use by the rails app - uncomment `Rails.application.credentials.payfast.merchant_id ` and wrap it in erb tags as instructed in the comments. ## Templates Update the `make_payment.html.erb` as instructed in the file. it should look like so: ```js <script> // set the uuid to uuid = @cart.payment_uid. surround @carts.payment_uid with erb tags const uuid = `<%= @cart.payment_uuid %>` window.payfast_do_onsite_payment({uuid}, function (result) { if (result === true) { // redirect success_path(@cart) window.location.href = `<%= success_cart_path(@cart) %>` } else { // Redirect to failure_path(@cart) window.location.href = `<%= failure_cart_path(@cart) %>` } }); </script> ``` ## Testing - payfast api allows only SSL communication from your server. inorder to test locally. you will have to use a tunneling service that allows you to expose your local development server to the internet. your rails development config has was modified by the generator to allow ngrok hosts to hit your rails server ```ruby config.hosts << /[a-z0-9-]+\.ngrok-free\.app/ ``` ## Contributing Thank you for considering contributing to our project! We welcome contributions from the community to help improve this project and make it better for everyone. ### Issues If you encounter any issues or bugs while using our project, please [open a new issue](https://github.com/mactunechy/payfast/issues) on GitHub. Please make sure to include detailed information about the problem, steps to reproduce it, and the environment in which you encountered it. ### Pull Requests We encourage pull requests from the community! If you have an improvement or new feature you'd like to contribute, please follow these steps: 1. Fork the repository and create a new branch for your feature or bug fix. 2. Make your changes and write tests to cover any new functionality. 3. Ensure that the existing tests pass and write additional tests for any bug fixes. 4. Commit your changes and push the new branch to your forked repository. 5. Submit a pull request to our main repository, including a detailed description of the changes you made and any relevant information. We will review your pull request as soon as possible and provide feedback if needed. We value your contributions and will work with you to ensure your changes are integrated smoothly. d Your contributions are essential to the success of this project, and we are grateful for your help in making it better for everyone. If you have any questions or need further assistance, feel free to reach out to us. Happy coding!
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.