task-control | Manages and automatically sends the tasks to Google

task.js

I am bit confused with Laravel conventions as I am new to this framework. I am following Jeffrey Way Laracasts videos he uses Plural for Controller names.

E.g.: PagesController, Cards Controller, PostsController

But if I refer official documentations of Laravel > Controllers and Laravel > Tutorials > Quick Start > Intermediate Task List it uses Singular names.

E.g.: PhotoController, TaskController

Can anybody please list down the official coding conventions for following entities?

Tables: posts, comments, post_comments or Post, Comment, PostComment

Columns: id, post_id, comment_id or id, postId, commentId

Controllers: PagesController, Cards Controller, PostsController or PhotoController, TaskController

Models: Pages, Cards, Posts or Page, Card, Post

i have a recursive function in my controllers that create a tree view table from an array, in this function i need to include task view when the if condition is true and this view is just a row of table with different param how can i access this view in a right way? problem is in crate_task_view function where i need task view pleas read codes before answering thanks... code is blow:

this is my TaskController

I'm working on a basic to-do application. Each to-do/task item gets listed as an input item in a Vue component, and the s are displayed with a v-for pointing to a tasks array.

I'm trying to allow the user to edit each task input, and upon changing the value, have this update the array item (rather than just the input itself). My @change event on the input is firing, but I'm at a loss as to what to do after this point.

https://jsfiddle.net/xbxm7hph/

HTML:

I'm currently working on an enterprise application that's performing a long non-linear tasks.

An abstraction of the workflow:

1. Gather neccessary information (can take minutes, but not always necessary)
2. Process data (always takes very long)
3. Notify several worker who post-process the result (in new tasks)

Now, I have created 2 services, that can solve step 1 and 2. As the services shouldn't know of each other, I want to have a higher order Component that coordinates the 3 steps of an task. Think of it as an Callable which sends the task to service one, wakes up again when service 1 returnes an result, sends it to service 2, ..., sends final result to all post-processors and ends task. But as it is likely to have 100'000s of queued tasks, I don't want to start 100'000s threads with task-control callables which even if being idle like 99.9% of the time still would be an massive overhead.

So got anybody an idea of controling this producer consumer queue-like pattern encapsulated in a task-object or somebody knows of an framework simplifying my concern?