Timeline for Repeater for blocks of Ruby
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 25, 2019 at 9:50 | history | edited | Toby Speight | CC BY-SA 4.0 | Spelling and grammar |
| Nov 19, 2019 at 14:36 | comment | added | Greg | Yeah, repeat method still returns the last result from the block, so you can assign it to any variable. | |
| Nov 19, 2019 at 14:24 | comment | added | Psycrow | Actually was just being a bit dense, you can assign the output of Repeater to a variable to have it accessible once it's finished running. Am going to experiment with this a bit and see how it handles real world applications | |
| Nov 19, 2019 at 11:28 | comment | added | Psycrow | This is interesting, and is the sort of thing that I had in mind. One question, is there a way to do this if I need to interrogate the result of the Repeater? For example, if I'm waiting until there is a record present in the database, but once it's there I want to use the values within the record to do something else. My first thought is to store result as an instance variable, any better ways to do it? | |
| Nov 18, 2019 at 20:08 | history | answered | Greg | CC BY-SA 4.0 |