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

    how to ignore one component error

    Help
    3
    8
    148
    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.
    • K
      k_magnai last edited by

      we work on same project by team but there is problem if one member get error on his working component then all project not work then other team member wait him to fix erro

      metalsadman 1 Reply Last reply Reply Quote 0
      • metalsadman
        metalsadman @k_magnai last edited by metalsadman

        @k_magnai if it’s just an eslint error then use options: { fix: true } on your quasar.conf.js>build>extendWebpack eslint-loader config. otherwise you guys should probably use collaborative tool like git, and work on separate branches so your codes don’t clash.

        1 Reply Last reply Reply Quote 0
        • K
          k_magnai last edited by

          Hi metalsadman tanks for your replay and your code demos also you write on other post i learning. use cloud9 realtime editor i don’t want to use git because its take a lot comparing code and our system special work on many domain and somethink special. Is there have any other way some lazy-compile or work like interpreted language when user visiting page that has error then show error.

          dobbel 1 Reply Last reply Reply Quote 0
          • dobbel
            dobbel @k_magnai last edited by

            @k_magnai

            You could disable( comment out) the component that causes the error…

            maybe this will be of help:
            https://github.com/webpack-contrib/eslint-loader/issues/23

            Working in the same dev environment sounds like one big mess you would like to avoid 😉 Good luck!

            1 Reply Last reply Reply Quote 0
            • K
              k_magnai last edited by k_magnai

              Hello Dobbel thanks your replay eslint is not my problem because i disabled it. can’t comment components because other developer working on it so its making mistakes. If employee make some syntax error on somewhere then all system not work. So i can’t see my result still other developer fix their error. In production version all system not work is really good but in Development version other developer’s error must stay in place…
              Many years i used cloud9 realtime editor and don’t use git sorry for that 😃

              1 Reply Last reply Reply Quote 0
              • K
                k_magnai last edited by

                also tried lazyload not help

                const routes = [
                {
                path: ‘/some-page’,
                component: () => import(‘pages/SomePage’)
                }
                ]

                metalsadman 1 Reply Last reply Reply Quote 0
                • metalsadman
                  metalsadman @k_magnai last edited by metalsadman

                  @k_magnai there’s really no way around that other than you or the other guy pull out the codebase and edit it locally. Unless you just want to imagine your result and just continue to code while the other guy fix his.

                  Imo better ask this in cloud9 forum.

                  1 Reply Last reply Reply Quote 0
                  • K
                    k_magnai last edited by

                    ok Thank you starting git 😃

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