No More Posting New Topics!

If you have a question or an issue, please start a thread in our Github Discussions Forum.
This forum is closed for new threads/ topics.

Navigation

    Quasar Framework

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    q-data-table shows "Duplicate presence of slot" error

    Help
    1
    3
    782
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      NikTang last edited by

      I’m trying to create a q-data-table with a column template I got an error :
      Duplicate presence of slot “col-mycol” found in the same render tree - this will likely cause render errors. (found in <QDataTable>)

              <q-data-table
                      :data="mainListData"
                      :config="mainListTableSettings.config"
                      :columns="mainListTableSettings.columns"
                      @refresh="reloadDataTable"
      
              >
                  <template slot='col-mycol' slot-scope='cell'>
                      can be anything text here - error occurs anyhow
                  </template>
              </q-data-table>
      

      I have already defined the column in the mainListTableSettings.columns as below.

                          {
                              label: 'MyCol',
                              field: 'mycol',
                              width: '200px',
                              style: {'text-align': 'center'}
                          }
      

      The mainListData does include a property ‘mycol’ in each row.

      Any ideas?

      1 Reply Last reply Reply Quote 0
      • N
        NikTang last edited by

        I’m using Quasar 0.14.7

        1 Reply Last reply Reply Quote 0
        • N
          NikTang last edited by

          updated vue.js to 2.5.13 and it’s solved. looks like the template engine has been changed in recent vue version.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post