permanent_records | Rails Plugin - soft-delete your ActiveRecord records | Web Framework library

by JackDanger Ruby Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | permanent_records Summary

permanent_records is a Ruby library typically used in Server, Web Framework, Ruby On Rails applications. permanent_records has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Rails Plugin - soft-delete your ActiveRecord records. It's like an explicit version of ActsAsParanoid

Support

Quality

Security

License

Reuse

Support

permanent_records has a low active ecosystem.

It has 234 star(s) with 58 fork(s). There are 13 watchers for this library.

It had no major release in the last 6 months.

There are 13 open issues and 39 have been closed. On average issues are closed in 187 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of permanent_records is current.

Quality

permanent_records has 0 bugs and 0 code smells.

Security

permanent_records has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

permanent_records code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

permanent_records is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

permanent_records releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

permanent_records saves you 390 person hours of effort in developing the same functionality from scratch.

It has 928 lines of code, 34 functions and 24 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of permanent_records

Get all kandi verified functions for this library.

permanent_records Key Features

No Key Features are available at this moment for permanent_records.

permanent_records Examples and Code Snippets

No Code Snippets are available at this moment for permanent_records.

Community Discussions

Trending Discussions on permanent_records

Rails - Globalize and Permanent_record dependent: :destroy callbacks

QUESTION

Rails - Globalize and Permanent_record dependent: :destroy callbacks

Asked 2017-Dec-09 at 14:22

In a Rails 4.2 project I use gem 'permanent_records' to handle records soft-deletion and gem 'globalize' for translations.

Globalize sets the following relationships between the translated Model and the Translation Model (source):

...

ANSWER

Answered 2017-Dec-05 at 09:46

There many ways to handle it. I wouldn't recommend to override dependent: :destroy.

best way to handle it by using paranoia gem which is a re-implementation of acts_as_paranoid. This gem takes care of soft delete with dependent destroy option. Refer: https://github.com/rubysherpas/paranoia
Override callback like this

Source https://stackoverflow.com/questions/47649748

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install permanent_records

You can download it from GitHub.
On a UNIX-like operating system, using your system’s package manager is easiest. However, the packaged Ruby version may not be the newest one. There is also an installer for Windows. Managers help you to switch between multiple Ruby versions on your system. Installers can be used to install a specific or multiple Ruby versions. Please refer ruby-lang.org for more information.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: