-
Notifications
You must be signed in to change notification settings - Fork 63
[Bug]: Root Child package name of library is required in parameter signature for ALS param suggestion functionality #1239
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
Comments
Hello @kevlar700, We'll open an internal issue to investigate, but that's probably a bug I would say. Thanks for the report, we'll keep you posted. Regards, |
Hello @kevlar700 |
I almost never use use. It compiles just fine. I don't get any warning from GNAT? You don't need to use a common parent package as it is automatically part of the name space. I guess I shall have to provide a package to demonstrate the issue. I'm not sure when though. |
Another issue that I have noticed is that if you edit a line with say ); at the end then completion does not work until ); is removed but perhaps that is by design. |
It would be great if you could provide a self-contained reproduced indeed, it will help us to see if we can improve our completion engine to handle that particular case. Regards, |
I think this one deserves a separate issue. Illustrating it with a GIF would also help us. Regards, |
Environment
Bug Summary and Reproducer
Bug Summary:
If you have a library procedure
Then ALS will handily fill out the params for you when you type the following from a main application so long as STM32.Devices.SPI is withed.
Then you can backspace the end (.SPI_T) and retype the . to get a list of possible values.
Steps to reproduce:
However if the procedure is the following ommiting the libraries root package name.
Then that functionality no longer works.
Expected behavior:
Is the advice to always include the root child package name in the library sources procedure signatures or is this a bug?
Configuration and Logs
Other VS Code Extensions
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: