From 3b989f9479b4d3b17a99c97423f4b2fdfc555cd1 Mon Sep 17 00:00:00 2001 From: Sam Bostock Date: Tue, 8 Nov 2022 21:39:56 -0500 Subject: [PATCH] Use guides, not edge guides --- guides/custom-enumerator.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/guides/custom-enumerator.md b/guides/custom-enumerator.md index 0bc3c65f..d2733a97 100644 --- a/guides/custom-enumerator.md +++ b/guides/custom-enumerator.md @@ -98,7 +98,7 @@ Code that is written after the `yield` in a custom enumerator is not guaranteed ### Cursor types -Cursors should be of a [type that Active Job can serialize](https://edgeguides.rubyonrails.org/active_job_basics.html#supported-types-for-arguments). +Cursors should be of a [type that Active Job can serialize](https://guides.rubyonrails.org/active_job_basics.html#supported-types-for-arguments). For example, consider: @@ -128,7 +128,7 @@ deserialization, the cursor would be corrupted as `:abc`, rather than To avoid this, job authors should take care to ensure that their cursor is serializable by Active Job. This can be done in a couple ways, such as: -- [adding GlobalID support to the cursor class](https://edgeguides.rubyonrails.org/active_job_basics.html#globalid) +- [adding GlobalID support to the cursor class](https://guides.rubyonrails.org/active_job_basics.html#globalid) - [implementing a custom Active Job argument serializer for the cursor class](https://guides.rubyonrails.org/active_job_basics.html#serializers) - handling (de)serialization in the job/enumerator itself ```ruby