@sibelly glad it helped, btw the logic is actually present in their server side pagination example https://v1.quasar-framework.org/vue-components/table#Server-side-pagination%2C-filter-and-sorting. you don’t need to call @update yourself, as i understood it, the call is made internally when you set the pagination.sync props.

@sibelly you should still define the complete pagination object props like what @CristalT shown above. also take a look at binary-state-sorting props https://forum.quasar-framework.org/topic/3389/solved-v1-table-sorting-strange-behaviour if you only want asc and desc sorting.
edit. looking at your repo you could also do update on your pagination before updating the other specific props within it.

...
onRequest (requestProp) {
       ...
           if (aux.page) {
              // update whole pagination object based on the props you passed in your request method first 
              this.pagination = requestProp.pagination
              // update other pagination props thereafter
              let total = aux.total_results
              let totalPages = aux.total_pages
              this.pagination.page = aux.page
              this.pagination.rowsPerPage = Math.round(total / totalPages)
              this.pagination.rowsNumber = aux.total_results
            }
...

try upgrading one of the repo that you’ve found https://v1.quasar-framework.org/start/upgrade-guide. upgraded a cloned Quasar + Laravel integration to newest verstion and it works https://github.com/metalsadman/quasar-laravel. the static page generated by quasar build still at old version though haven’t updated my pages to new v1 components yet. you can test using quasar dev if you want to see the v1 generated version.

What test you are trying to do though? here’s their testing docs https://testing.quasar-framework.org/. probably take a look into vue js testing utils too https://vue-test-utils.vuejs.org.

he is already using Vuelidate though. @maxant try looking into Vee-Validate https://baianat.github.io/vee-validate/. It’s a template based validation library if quasar’s internal one is not enough in your case.

@rconstantine It’s a component now called QPageScroller https://v1.quasar-framework.org/layout/page-scroller#Introduction.

@CristalT oh, glad it helped you :).

you could use codesandbox or codepen sample https://codepen.io/TruckTurner/pen/qqpRyq.
I think at report-params component is where you should listen to your child component emitted event.

...
  <report-params @workflow-fac-change="doSomethingWithTheEmittedData"/>
...
methods: {
  doSomethingWithTheEmittedData(data) {
    //where data is facility
  }
}
...

i’m not sure about the use of root coz usually i’ll just use this.$emit(…) to pass a data back to parent component. some vue docs https://vuejs.org/v2/guide/components.html#Listening-to-Child-Components-Events & https://vuejs.org/v2/guide/components-custom-events.html.

I’ve tested something like this on a previous forum issue, though this was pre v1, i’ll just copy paste my code to give you an idea.
frontend:

<template>
  <q-page class="row justify-center">
    <q-uploader
      extensions=".jpg, .png"
      multiple
      :upload-factory="uploadFile"
      ref="uploader"
      auto-expand
      url=""
      stack-label="upload image"
    />
  </q-page>
</template>

<script>
export default {
  data () {
    return {
      uploadPercentage: 0
    }
  },
  methods: {
    uploadFile (file, updateProgress) {
      const fd = new FormData()
      fd.append('file', file)
      updateProgress(0)
      return new Promise((resolve, reject) => {
        this.$axios.post(process.env.api + '/upload',
          fd,
          {
            headers: { 'Content-Type': 'multipart/form-data' },
            onUploadProgress: (progressEvent) => {
              updateProgress(Math.round((progressEvent.loaded / progressEvent.total) * 100) / 100)
            }
          })
          .then(res => {
            resolve(file)
          })
          .catch(err => reject(err))
      })
    }
  }
}
</script>

laravel backend controller:

...
class UploadController extends Controller
{
  ...  
    public function upload(Request $request)
    {

        // $files = $request->file;
        $request->file->storeAs('uploads', uniqid('img_') . $request->file->getClientOriginalName());
        // image will be stored at storage/app/public/uploads
        // return $request;
        // if (!empty($files)) {
        //     foreach ($files as $file) {
        //         Storage::put($file - getClientOriginalName(), file_get_contents($file));
        //         return ['file' => $file];
        //     }
        // }

        // return response()->json([
        //     'request' => $request,
        //     'message' => 'idunno',
        // ]);
    }
}
...
laravel route
Route::post('/upload', 'UploadController@upload');

@kp did you tried yarn instead? since i read in their discord that npm does not work properly on windows so yeah, just tried yarn and it worked for me with this upgrade.