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

Autocomplete of class parameters and built-in functions inside classes does not work #769

Open
nscheer opened this issue Sep 3, 2021 · 4 comments

Comments

@nscheer
Copy link

nscheer commented Sep 3, 2021

What Versions are you running?

OS Version: Windows 10 Pro 20H2 / WSL2 with Debian 10
VSCode Version: 1.60.0
Puppet Extension Version: 1.3.0
PDK Version: 2.2.0 (installed in WSL2 Debian)

What You Are Seeing?

In an empty .pp file, built-in function are auto completed, so when I type something like

$x = spl

"split" is suggested. After autocompleting the function it shows its various signatures as well, as I have activated the puppetstrings feature.

But inside a class, built-in functions are not autocompleted anymore:

# Class: test
#
#
class test {
  $x = sp
}

Here I only get "no suggestions".

Furthermore, vscode knows the core data types for class parameters, but does not seem able to autocomplete them:

# Class: test
#
#
class test (
  Str
){

}

So no suggestion for "String" is shown here. If I complete the parameter and hover over "String" it displays "The String core data type".

What is Expected?

Autocompletion of built-in functions inside classes should work. It would be nice if types could be autocompleted as well.

How Did You Get This To Happen? (Steps to Reproduce)

Navigate to an empty folder in WSL2 and open vscode using code .. Create a new file "test.pp".

@sanfrancrisko
Copy link

Thanks for reporting @nscheer - I've been able to reproduce this

@CryoRig
Copy link

CryoRig commented Oct 19, 2021

Any news on this? Have the same Issue...

@sanfrancrisko
Copy link

@CryoRig the ticket is in our backlog to be worked upon. Unfortunately, given resourcing on the team, we're unable to pick this up in the near future. Monday is the day we focus on issues raised across the 24 repositories under our remit and it's in our pipeline to tackle as soon as we can.

@CryoRig
Copy link

CryoRig commented Nov 1, 2021

Thank you for the update

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

No branches or pull requests

4 participants