Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide a method to do (n) number of batches #58

Open
jjeaton opened this issue Sep 21, 2016 · 5 comments
Open

Provide a method to do (n) number of batches #58

jjeaton opened this issue Sep 21, 2016 · 5 comments

Comments

@jjeaton
Copy link
Contributor

jjeaton commented Sep 21, 2016

The use case here is if you wanted to create 100 posts, you don't have existing objects to query, you need some way to say, run this 100 times.

@jjeaton jjeaton changed the title Provide a method to do n number of batches Provide a method to do (n) number of batches Sep 21, 2016
@zachwills
Copy link
Contributor

I don't think we currently support a process for creating something. We would probably want to nail down how that should function, implement it, then implement this. Unless this task is supposed to add that functionality?

@zachwills zachwills added this to the Future Release milestone Sep 21, 2016
@zachwills
Copy link
Contributor

Perhaps the better question would be: is this applicable only in the instance of creating items through Locomotive? If it is relevant in the context of processing existing items we could implement this without adding the create functionality.

@jjeaton
Copy link
Contributor Author

jjeaton commented Sep 21, 2016

this shouldn't have anything to do with creating. that was just one example use case. if someone wanted to send 10 emails or log "Hamburger" to the error_log 10 times, then this is what they would use.

@zachwills
Copy link
Contributor

Ah that makes sense! Thanks for the clarification. Right now the plugin pretty much revolves around looping through existing posts. Since this issue introduces a new approach (processing something without querying for data first) I think we should plan the approach first.

@jjeaton
Copy link
Contributor Author

jjeaton commented Sep 21, 2016 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants