github-migration
/
guard-rails
1
0
Fork 0
Code Issues 6 Pull Requests 2 Packages Projects Releases Wiki Activity

Depreciation Warning run_on_change #17

New Issue
Open
opened 2012-06-24 04:05:51 +00:00 by deLeon · 1 comment
deLeon commented 2012-06-24 04:05:51 +00:00 (Migrated from github.com)
Copy Link

This is really about about guard/guard-rails
There are depreciation warnings about run_on_change. I noticed you already updated this gem (johnbintz/guard-rails); can you update the guard/guard-rails gem as well? I couldn't submit an issue there. Is that gem unsupported now?

DEPRECATION: Starting with Guard v1.1 the use of the 'run_on_change' method in the 'Guard::Rails' guard is deprecated.
Please consider replacing that method-call with 'run_on_changes' if the type of change
is not important for your usecase or using either 'run_on_modifications' or 'run_on_additions'
based on the type of the changes you want to handle.
For more information on how to update existing guards, please head over to:
https://github.com/guard/guard/wiki/Upgrade-guide-for-existing-guards-to-Guard-v1.1

This is really about about guard/guard-rails There are depreciation warnings about run_on_change. I noticed you already updated this gem (johnbintz/guard-rails); can you update the guard/guard-rails gem as well? I couldn't submit an issue there. Is that gem unsupported now? > DEPRECATION: Starting with Guard v1.1 the use of the 'run_on_change' method in the 'Guard::Rails' guard is deprecated. > Please consider replacing that method-call with 'run_on_changes' if the type of change > is not important for your usecase or using either 'run_on_modifications' or 'run_on_additions' > based on the type of the changes you want to handle. > For more information on how to update existing guards, please head over to: > https://github.com/guard/guard/wiki/Upgrade-guide-for-existing-guards-to-Guard-v1.1
johnbintz commented 2012-06-24 12:28:27 +00:00 (Migrated from github.com)
Copy Link

No, just been busy. I'll get to it when I get the chance.

No, just been busy. I'll get to it when I get the chance.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
jarmo/master
robotex82/better-engine-support
linux-support
v0.1.1
v0.1.0
v0.0.3
v0.0.2
v0.0.1
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: github-migration/guard-rails#17
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?