V

vestal_versions

Settings | Report Duplicate

0

I Use This!

Inactive

Commits : Listings

Analyzed 15 days ago. based on code collected 15 days ago.

Commit Message	Contributor	Files Modified	Lines Added	Lines Removed	Code Location	Date
May 31, 2023 — May 31, 2024 Showing page 7 of 12 Search / Filter on:
Added a failing test for storing the user responsible for updating a record.	laserlemon	More...				over 14 years ago
Added user-related column to the test schema.	laserlemon	More...				over 14 years ago
Updated the .gitignore file to match the new Jeweler default.	laserlemon	More...				over 14 years ago
Beefed up the changes tests a bit further and stopped hard-coding the version numbers.	laserlemon	More...				over 14 years ago
Added all sorts of tests for the changes_between method.	laserlemon	More...				over 14 years ago
Rewrote the changes test and even squashed a bug that the new tests exposed.	laserlemon	More...				over 14 years ago
Removed the associations and bookkeeping modules until I can dream up the correct approach.	laserlemon	More...				over 14 years ago
Simplified the revert_to method to remove duplication with changes_between.	laserlemon	More...				over 14 years ago
Added some cleanup to the Hash#append_changes method to make sure that all changes are actually meaningful.	laserlemon	More...				over 14 years ago
Renamed and restructured the generator.	laserlemon	More...				over 14 years ago
Added the ability to "reset" to a version (as opposed to "revert") which actually removes records from the version history.	laserlemon	More...				over 14 years ago
Restructured the storage of vestal_versions options for reuse in future modules.	laserlemon	More...				over 14 years ago
Added the ability to run a configuration initializer to DRY up options across multiple models.	laserlemon	More...				over 14 years ago
Fixed the :if and :unless symbol argument handling to pass the proper receiver.	laserlemon	More...				over 14 years ago
Refactored the control blocks to extract out the common structure.	laserlemon	More...				over 14 years ago
Added conditional version creation via :if and :unless options.	laserlemon	More...				over 14 years ago
DRYed up the original create_version? method to utilize the version_changes method.	laserlemon	More...				over 14 years ago
Just a little simplification of an overly-complex conditional.	laserlemon	More...				over 14 years ago
Just cleaned up the versions association methods.	laserlemon	More...				over 14 years ago
Added the ability to revert to a tag into the versions association methods.	laserlemon	More...				over 14 years ago
Fixed the test schema creation to allow for version tagging.	laserlemon	More...				over 14 years ago
Added the ability to tag specific versions.	laserlemon	More...				over 14 years ago
Re-added the ability to revert to a symbol argument, representing an association method.	laserlemon	More...				over 14 years ago
Allowed for custom table names for the version model in the association methods module.	laserlemon	More...				over 14 years ago
Added a default scope to the version model, in order to ascend by number.	laserlemon	More...				over 14 years ago
Stopped aliasing Version#number as Version#version.	laserlemon	More...				over 14 years ago
Cleaned up a couple unnecessary parentheses.	laserlemon	More...				over 14 years ago
Upon updating a version, notify the version that the changes will be... changing.	laserlemon	More...				over 14 years ago
Added control structures for customized handling of version creation.	laserlemon	More...				over 14 years ago
Renamed the needs_version? method to create_version? for consistency with the control features (that I'm about to add).	laserlemon	More...				over 14 years ago

←
1
2
3
4
5
6
7
8
9
10
11
12
→