Add runnable and parallel pkgs #3
No reviewers
Labels
No labels
🤖 fix nits
🧠 ai fix nits
autorelease
bug
do not merge
documentation
duplicate
enhancement
good first issue
help wanted
invalid
merge when ready
no changelog
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
golibs/go-tasks!3
Loading…
Reference in a new issue
No description provided.
Delete branch "ta/runnable"
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?
Before this PR
After this PR
==COMMIT_MSG== Add runnable and parallel pkgs ==COMMIT_MSG==
Possible downsides?
Generate changelog in
changelog/@unreleasedType (Select exactly one)
Description Add runnable and parallel pkgs
Check the box to generate changelog(s)
✅ Successfully generated changelog entry!
Need to regenerate?
Simply interact with the changelog bot comment again to regenerate these entries.
📋Changelog Preview
✨ Features
@ -0,0 +22,4 @@type RunFn func(ctx context.Context) error// Runnable is a named object that can be run.type Runnable interface {Should we call this a Task?
I would like to root primitive that we use across jobs/runnables to be shared. We could make this "Runnable", or we could make this "Task" and then then "Runnable" package would use the Task package.
@ -0,0 +24,4 @@// Runnable is a named object that can be run.type Runnable interface {Run(ctx context.Context) errorName() stringWe should compose this:
type Runnable interface { Run(ctx context.Context) error }
type NamedRunnable interface { Runnable GetName() string }
@ -0,0 +12,4 @@// See the License for the specific language governing permissions and// limitations under the License.package runnableI could see us removing this entire file FWIW. I really depends how server integration looks
👍