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

Legacy config file version found: "0.2", upgrade to "0.2" #1729

Closed
4 of 18 tasks
dshemin opened this issue Sep 21, 2021 · 3 comments · Fixed by #1730
Closed
4 of 18 tasks

Legacy config file version found: "0.2", upgrade to "0.2" #1729

dshemin opened this issue Sep 21, 2021 · 3 comments · Fixed by #1730

Comments

@dshemin
Copy link

dshemin commented Sep 21, 2021

Info

Kind of Issue

  • runtime - command-line tools
  • building / compiling
  • security
  • change in behavior
  • crash / error

Which Tool or library

  • cspell -- the command-line spelling tool
  • cspell-tools -- used for building dictionary files
  • cspell-lib -- library that does the actual spell checking.
  • cspell-trie -- tool for working with trie files.

Which Version

Version: 5.10.1

Issue with supporting library?

  • No
  • cspell-glob -- library for matching glob patterns
  • cspell-io -- thin file i/o library
  • cspell-trie-lib - trie lib
  • cspell-trie2-lib - trie lib alternate format

OS:

  • Macos
  • Linux
  • Windows
  • Other

version:

Ubuntu 20.04.3 LTS

Bug Description

Describe the bug

When I try to import one config into another I've got strange warning:

Legacy config file version found: "0.2", upgrade to "0.2"

To Reproduce

Steps to reproduce the behavior:

  1. Take two attached configs
  2. cspell --config a.yaml "**"
  3. See warning

Configs:

a.yaml

version: 0.2
language: en
import:
  - b.yaml

b.yaml

version: 0.2
language: en

Expected behavior

No warning should be shown

Screenshots

Screenshot from 2021-09-21 10-16-03

@Jason3S
Copy link
Collaborator

Jason3S commented Sep 21, 2021

Thank you an excellent example.

@Jason3S
Copy link
Collaborator

Jason3S commented Sep 21, 2021

@dshemin,

It is expecting a string and not a number.

Try:

version "0.2"
language: en

@github-actions
Copy link
Contributor

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants