PaperTrail
Simple Form
Our great sponsors
PaperTrail | Simple Form | |
---|---|---|
18 | 13 | |
6,697 | 8,191 | |
0.5% | 0.1% | |
5.9 | 5.7 | |
3 months ago | 12 days ago | |
Ruby | Ruby | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
PaperTrail
-
historical data and "point in time" data modeling techniques, advice.
if the source (web) application makes their own audit tables. ex: our ruby on rails application uses the paper-trail gem
-
Best rails tools to automatically handle logging of things like all a user's actions, or changes to a record in a module - primarily for audit purposes.
Start with https://github.com/paper-trail-gem/paper_trail
-
Inventory/Sales Management module built on a Rails app - what would be the best way to "version" updates made against an SKU.
We use paper_trail for this
-
is there a gem for tracking adhoc rails console changes
I think you could use that in conjunction with the paper_trail gem, as /u/GreenCalligrapher571 mentioned, which is also a good suggestion. As an additional note, when changing records in production while using the paper_trail gem, I suggest wrapping your database-mutating statements executed in the rails console within a whodunnit block, so PaperTrail.request(whodunnit: 'Dorian Marié') { widget.update name: 'Wibble' } or something rather than just widget.update name: 'Wibble'. Or, if you have some sort of issue-tracking / ticketing system, you could set the whodunnit value to the ticket number or whatever, and then anyone who wants to know why the records are in the state they're in can consult that ticket, which hopefully has additional relevant context.
-
History Tracking With Postgres
For a while we did this using the paper-trail gem. This was a very simple way to add a few lines of code to keep track of all of the changes made to an ActiveRecord model. But it came with one drawback. Every change to the data had to be done through ActiveRecord. There are often times when this makes an app vulnerable to a race condition. I’ll use a contrived example so as not to share any real code from our client’s app.
-
Adding soft delete to a Phoenix Commanded (CQRS) API
In most designs, this would probably not be possible unless a table tracking extension is being used in an ORM. Even with change tracking enabled through extensions like paper trail or Django simple history, it can be tricky to restore deleted entities. Object tracking would need to have been enabled before it is needed to ensure the data is still around to be restored.
- Looking for a Rails Gem that Audits Manual Database Changes
-
Temporality/time-travelling in DB with ActiveRecord?
Maybe you are looking for the papertrail gem? https://github.com/paper-trail-gem/paper_trail
- Looking for an observer gem
Simple Form
-
Internationalize and Humanize your Ruby on Rails application
I also tend to use gems like simple_form to generate my form HTML, and this saves me from having to maintain a lot of view code to outputting translated content onto forms. Also simple_form has it's own i18n convention that compliments the Rails default pretty well.
- AppDev Week 2
-
Rails simple_form gem: Unable to render validation messages
I followed the RailsCasts tutorial and its GitHub page to set up the gem in my application and used it for all of the models in my application. It was working perfectly fine showing the default error message at the top and the validation message at the bottom of their respective fields.
-
Updating a Booking Status
Okay now for those "buttons". We don't want just a normal button or link though. This is where we need the booking update form. Let's use simple_form_for (check out the docs here).
-
#1 Made easy form in Rails with Simple Form - Gem Weekly
There are many ways to create a form in Rails, whether you want to create a form with Form builder from Rails itself or maybe using third party gem like simple_form. Of course, simple_form is not the only option we have to build form in rails, there are alternatives out there such as formtastic, cocoon, nested_form, etc. However, in this post I'm going to give you a basic use case to use simple_form in Rails application.
-
Reusable form elements
I usually go with simple_form, I customise my forms by configuring it and letting it handle the repeated rendering.
- How to wrap select field in div in SimpleForm?
-
Styling Simple Form forms with Tailwind
Simple Form gem
-
From partials to ViewComponents: writing reusable front-end code in Rails
The biggest unclear area that we saw related to view components were forms. There were glimpses of compatibility issues with Rails form helpers in the documentation and we saw a recent effort of the team to mitigate them. Moreover, we were used to building forms with Simple Form which added another variable to the equation. And, in general, we considered the Rails form builders (as well as the Simple Form builder) a system of form-related components in the first place so we were unsure how this would fit into the View Components ecosystem or whether we should even try to do that.
-
Simple Form
Learn more about simple form: 1) https://github.com/heartcombo/simple_form 2) https://www.youtube.com/watch?v=NfZk74R2Oi4&t=5s
What are some alternatives?
Audited - Audited (formerly acts_as_audited) is an ORM extension that logs all changes to your Rails models.
Formtastic - A Rails form builder plugin with semantically rich and accessible markup.
Paranoia - acts_as_paranoid for Rails 5, 6 and 7
Rails Bootstrap Forms - Official repository of the bootstrap_form gem, a Rails form builder that makes it super easy to create beautiful-looking forms using Bootstrap 5.
Logidze - Database changes log for Rails
Cocoon - Dynamic nested forms using jQuery made easy; works with formtastic, simple_form or default forms
mongoid-history - Multi-user non-linear history tracking, auditing, undo, redo for mongoid.
Reform - Form objects decoupled from models.
ActsAsParanoid - ActiveRecord plugin allowing you to hide and restore records without actually deleting them.
ActiveForm - Create nested forms with ease.
Discard - 🃏🗑 Soft deletes for ActiveRecord done right
Abracadabra