A tiny tags editor written in vanilla JavaScript
React Tags Editor
List of standard SVG tags.
HTML void elements are not the only self-closing tags. This includes common SVG self-closing elements as well.
Work with IANA language tags.
A react supported html attributes store keyed by their tags
List of standard HTML tags
a few common utility template tags for ES2015
Full BCP 47 language subtag data from the official IANA repository, in JSON format with multiple indices.
A lightweight React FormatBuilder component + Modal for building dynamic object formats (chips/tags editor)
Get all git semver tags of your repository in reverse chronological order.
Generic JSDoc-like comment parser
Datadog CI plugin for `sarif` commands
m3u8 parser
Core logic for the tags-input widget implemented as a state machine
Datadog CI plugin for `gate` commands
TypeScript definitions for common-tags
Gatsby Telemetry
lezer-based HTML grammar
```bash npm install @contentful/field-editor-tags ```
Match BCP 47 language tags with language ranges per RFC 4647
A document head manager for React
Parses well-formed HTML (meaning all tags closed) into an AST and back. quickly.
Parse and stringify BCP 47 language tags
ID3 tags editor for the command line written in Ruby.
Include help text on a page based on its slug. Includes 1 simple tag and a basic content editor
A modified version of Basecamp's Trix Editor for use in scientific applications. Modifications include: Superscript tags, Subscript tags, text underlining, notation sympols, registration symbols, and removal of quote and code blocks
rcodetools is a collection of Ruby code manipulation tools. It includes xmpfilter and editor-independent Ruby development helper tools, as well as emacs and vim interfaces. Currently, rcodetools comprises: * xmpfilter: Automagic Test::Unit assertions/RSpec expectations and code annotations * rct-complete: Accurate method/class/constant etc. completions * rct-doc: Document browsing and code navigator * rct-meth-args: Precise method info (meta-prog. aware) and TAGS generation
Do you like to search through code using ag, ack, grep, pt, or rg? Good! This tool is for you! Zoom adds some convenience to grep-like search tools by allowing you to quickly open your search results in your editor of choice. When looking at large code-bases, it can be a pain to have to scroll to find the filename of each result. Zoom prints a tag number in front of each result that grep outputs. Then you can quickly open that tag number with Zoom to jump straight to the source. Zoom is even persistent across all your sessions! You can search in one terminal and jump to a tag in another terminal from any directory!
Rails-AI-Bridge introspects your Rails application and exposes structure to AI assistants via static context files and a live Model Context Protocol (MCP) server. It classifies Active Record models semantically (Core, Join, Supporting), optionally surfaces non-ActiveRecord Ruby classes under app/models (tagged POJO/Service), and integrates with editors and assistants such as Claude, Gemini, Cursor, and Windsurf.
# 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.