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

state-selector is giving a false positive yaml-schema error #886

Open
Grumblezz opened this issue Oct 13, 2024 · 2 comments
Open

state-selector is giving a false positive yaml-schema error #886

Grumblezz opened this issue Oct 13, 2024 · 2 comments

Comments

@Grumblezz
Copy link

Grumblezz commented Oct 13, 2024

Problem/Motivation

With the update to 2024.10 the syntax of many things are updated, but the following one seems to be a false positive:
image

In my scripts.yaml:

state_test:
  alias: State Test
  sequence: []
  fields:
    entity_state:
      selector:
        state:
          entity_id: update.home_assistant_core_update
      name: Entity State
      default: 'off'
  description: ''

The validation error is showing 2 false errors:

Missing property "action"
Property state is not allowed.

When reviewing the https://www.home-assistant.io/docs/blueprint/selectors/#state-selector then it looks OK. And when I create a new script via the UI with the state selector then the errors are also shown in the VSCode addon.

Expected behavior

The current selector example should not show a yaml-schema error.

Actual behavior

The current selector example is showing a yaml-schema error.

Steps to reproduce

Use the example from above to get the same yaml-schema error.

Proposed changes

Please fix the yaml-schema error.

@wltng
Copy link

wltng commented Oct 14, 2024

There are more situations where valid yaml is considered invalid (since the new yaml options, and vscode 5.17+)
E.g. #882

Unfortunately I’m being told it is not a problem…

@frenck
Copy link
Member

frenck commented Oct 14, 2024

@wltng Your situation wasn’t related to this report.

../Frenck

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants