Apologies for the big PR. I am missing some test cases, but I will come back for them when I work on quick actions.
This PR extracts symbols from document using @aws/fully-qualified-names to improve Q's suggestions. The execution will be run by workers to increase resilience. Since the implementation of workers and the fqn library are platform dependent, we need to split up the entry points so build system can bundle the appropriate files.
Each environment will have its own worker file that takes care of importing fqn and running the code. The exported FqnWorkerPool will use this worker. Build systems are then able to locate the right bundle based on the "target" option
[x] Browser (didn't get TextDecoder error, which meant it was the bundler version)
[x] Toolkits (vscode, vs)
Note
I did reference the vscode logic so dedup, sort and limit are all based on that implementation
Description
Apologies for the big PR. I am missing some test cases, but I will come back for them when I work on quick actions.
This PR extracts symbols from document using
@aws/fully-qualified-namesto improve Q's suggestions. The execution will be run by workers to increase resilience. Since the implementation of workers and the fqn library are platform dependent, we need to split up the entry points so build system can bundle the appropriate files.Each environment will have its own worker file that takes care of importing fqn and running the code. The exported
FqnWorkerPoolwill use this worker. Build systems are then able to locate the right bundle based on the "target" optionTextDecodererror, which meant it was the bundler version)Note
Next up
License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.