TSBufDisable and disabling module not working properly on some filetypes about nvim-treesitter HOT 7 CLOSED

also TSModuleInfo doesn't give informations about linked filetypes (like javascriptreact)

from nvim-treesitter.

Not sure but it seems javascriptreact is actually not defined anywhere in the code.

from nvim-treesitter.

I remember that someone had a complaint about the file type changed by a plugin. Nvim-treesitter gave error messages when trying to use the parser for the buffer it was attached to but now with a different file type. After that typescriptreact was added to the used_by of the parser. Can you disable for JavaScript react once it's registered as used_by?

from nvim-treesitter.

I will look into it later today if i'm not too tired :) i think javascriptreact is indeed not set as used_by in the js parser.
Also i should look into the js queries to see if they handle jsx stuff.

from nvim-treesitter.

I don't know if this is related. setup behaves really weird, I tried to implement a globale disable option but it kind of fails to disable some modules once they are activated. Also when running setup a second time some disabled modules don't get disabled once they have been enabled by enable_all. Especially, the highlighting module since the refactor in upstream apparently is not disabled by the modules detach function.

function M.setup(user_data)
  for name, data in pairs(user_data) do
    if name == 'ensure_installed' then
      config.ensure_installed = data
      require'nvim-treesitter.install'.ensure_installed(data)
    else
      data.disable = vim.list_extend(data.disable or {}, user_data.disable or {})
      config.modules[name] = vim.tbl_deep_extend('force', config.modules[name] or {}, data)

      recurse_modules(function(_, _, new_path)
        if data.enable then
          enable_all(new_path)
        end
        for _, lang in ipairs(config.modules[name].disable) do
          disable_mod_conf_autocmd(new_path, lang)
        end
      end, config.modules[name]) -- note that i would use this instead of config.modules (how did this even work?)
    end
  end
end

from nvim-treesitter.

@kyazdani42 is this still an issue?

from nvim-treesitter.

looks like it has been fixed

from nvim-treesitter.