Search Results for "using class net.sourceforge.jtds.jdbc.driver"

factory_bot is a fixtures replacement with a straightforward definition syntax, support for multiple build strategies (saved instances, unsaved instances, attribute hashes, and stubbed objects), and support for multiple factories for the same class (user, admin_user, and so on), including factory inheritance. factory_bot provides a framework and DSL for defining and using factories - less error-prone, more explicit, and all-around easier to work with than fixtures. Each factory has a name...

DataTables is a nifty jQuery plugin that adds the ability to paginate, sort, and search your HTML tables. When dealing with large tables (more than a couple of hundred rows) however, we run into performance issues. These can be fixed by using server-side pagination, but this breaks some DataTables functionality. ajax-data tables-rails is a wrapper around DataTables ajax methods that allow synchronization with server-side pagination in a Rails app. It was inspired by this Railscast. I needed...

Pundit (varvet/pundit) is a Ruby gem that provides a simple and effective framework for adding authorization logic to Rails (or other Ruby) applications. It centers around policy classes—one policy per model or resource—that define what actions a given user is permitted to perform (e.g., show?, update?, destroy?). Each policy method returns a boolean, and can be structured using combinators or shared logic to keep things DRY. In controllers and views, Pundit provides helpers like authorize...

Rpg.NET is an API built using the .NET Framework for both improving performance and enhancing the RPG Maker series (XP, VX, and VXA). Contained within are various functions and classes that extend the ability of RPG Maker in areas such as graphics, audio, and Windows API interop. Included is a Ruby script that is the wrapper around the library, so it can be used as any other script within your game.

CanCan is an authorization library for Ruby on Rails that helps manage user permissions in a clean and consistent way. It centralizes all authorization logic in a single Ability class, where you define what actions each type of user can or cannot perform on different resources. Developers then use helpers like authorize! in controllers or can? in views to enforce those rules without scattering permission logic across the application. It supports defining permissions using conditions, allowing...