OutOfFocus4
OutOfFocus4
I am experiencing this issue, too. > Unable to load schema from 'https://gitlab.com/gitlab-org/gitlab/-/raw/master/app/assets/javascripts/editor/schema/ci.json': Request vscode/content failed unexpectedly without providing any details. YAML(768) I can access the schema using curl: ```...
I tried on a Mac and it didn't work, either. I can reach the schema store. 
I did some more investigating and found that if I uninstall the extension and delete the JSON schema cache from my filesystem, the cache will be regenerated if I install...
I renamed `.gitlab-ci.yml` to `a.gitlab-ci.yml`, and it started to work. Shouldn't `.gitlab-ci.yml` work with `*.gitlab-ci.yml`, since `*` can match zero characters?
> @OutOfFocus4 Can you test latest `0.19.2`? It supposed to work. I updated to `0.19.2`. `.gitlab-ci.yml` still isn't seen as a GitLab CI configuration file. 
I just tried again on Windows, MacOS, and Ubuntu. Windows 10:  MacOS:  Ubuntu:  Autocomplete and linting work in `a.gitlab-ci.yml`, but not in `.gitlab-ci.yml` with identical...
As I demonstrated in my screenshots in [my screenshots above](https://github.com/redhat-developer/vscode-yaml/issues/508#issuecomment-849615238), the extensions works with files named `a.gitlab-ci.yml`, but not `.gitlab-ci.yml`. Is the globbing using an OS-level search function, and my...
I just updated to 0.20.0, and everything is working again. Should I close this issue, or keep it open until a root cause has been identified and regression tests are...