You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
STM32.SPI.Run.Configure (SPI : in STM32.Devices.SPI.SPI_T);
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.
STM32.SPI.Run.Configure ( Ctrl=>Space
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.
STM32.SPI.Run.Configure (SPI : in Devices.SPI.SPI_T);
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
I expect that this is the current behaviour for any configuration but can provide logs if required. The current behaviour may even be the best that can be expected?
Other VS Code Extensions
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
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: