A Gem containing shared code for the CCS Crown Marketplace projects, for example view helpers

Have you ever asked yourself, "Is this method even being used?!" Or, "What the heck is this method receiving?" Does your application use Rails? If the answers these questions are yes, this gem may be of use to you! Large applications can accrue cruft; old methods that might once have been important, but are now unused or code that is difficult to understand, but dangerous to refactor. Unfortunately, software is _complex_ and sometimes it's unclear what's really going on. This adds maintenance burdens, headaches, and uncertainty. This gem aims to give you a couple tools to make it easier to know what (and how) your code is being used (or not). CruftTracker supports Rails versions 5.2 to 6.1 at this time. As of now the gem only supports MySQL, but contributions for Postgres or other DBMS would be welcome.

Import your CSV files in multiple steps

Hydra models for CUL repository apps.

Shared Rubocop config used at DashBrains

A Rails 5 & Rails 6 plugin for handling Db2 API request by using JWT token.

Degica style guides

Auth0 authentication for devise

Implementation of DPoP (Demonstrating Proof-of-Possession at the Application Layer) for Ruby and Rails

Rails extension for scheduling drip campaigns

Data Update Tool facilitates efficient bulk-updating of data in Ruby applications

The standard Rubocop rules for the DVLA

It is customizable and flexible scaffold who support sort and the pagination.

Extensions to Aws::Record for working with DynamoDB.

Development support for Ruby' Gem.

Simplify the way you fetch model data, making coding smoother and data exporting handling a breeze

EMF to SVG conversion in Ruby.

Ephemeron improves the performance of your app. It takes on itself the persistence of the ActiveRecord objects. It protects you from saving the same object many times. It checks whether a fetched from a database object was used. It allows you to eliminate the controller's before_actions that are unnecessarily called. Ephemeron works in the context of the thread and does the bulk of its job (i.a. persistence) at the end of the thread's lifecycle. Although, you can trigger the finalization at any given moment. You don't have to make a distinction in the code for the part that is responsible for the domain logic and the other responsible for the application layers.

Rubocop style checking for ERGOMENTUM projects.

Event sourcing toolkit using Rails and ActiveJob