Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extension README has errors in config file names #142

Closed
Jakub-CZ opened this issue Jul 12, 2021 · 2 comments · Fixed by #149
Closed

Extension README has errors in config file names #142

Jakub-CZ opened this issue Jul 12, 2021 · 2 comments · Fixed by #149
Assignees
Labels
documentation Improvements or additions to documentation released on @release-0.14.0 released

Comments

@Jakub-CZ
Copy link

Describe the bug
In the section File Extensions in the extension README (and in Extension Marketplace), the config file name proc_conf.json is incorrect; it should be proc_grps.json instead.

To Reproduce
N/A

Expected behavior
proc_conf.json should not occur anywhere in the docs.

Screenshots
image

Platform

  • Plugin version: 0.13.0

Additional context
N/A

@slavek-kucera slavek-kucera added the documentation Improvements or additions to documentation label Jul 12, 2021
@slavek-kucera slavek-kucera self-assigned this Jul 15, 2021
slavek-kucera added a commit to slavek-kucera/che-che4z-lsp-for-hlasm that referenced this issue Jul 15, 2021
@slavek-kucera slavek-kucera linked a pull request Jul 16, 2021 that will close this issue
@github-actions
Copy link

🎉 This issue has been resolved in version 0.14.0-beta.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@github-actions
Copy link

🎉 This issue has been resolved in version 0.14.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation released on @release-0.14.0 released
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants