Skip to content

Conversation

kylewalke
Copy link
Contributor

No description provided.

'precise',
);

// TODO: remove this. Why doesn't the symbol manager have the symbol table?
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is what I'm stuck with on getting the web hovers to work :/

* Try to find a symbol by directly parsing the document when symbol manager doesn't have it
* This is a fallback mechanism for when symbol processing hasn't completed yet
*/
private async tryDirectDocumentParsing(
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Definitely don't think we need to be reparsing the whole doc. Something else is missing.

kylewalke and others added 3 commits September 23, 2025 17:40
- Remove FileSystemWatcher from web LanguageClient to prevent cloning errors
- Simplify initialization options to only include serializable data
- Preserve output channel functionality through notification handlers
- Fix web extension launch configuration to use correct entry points
- Update package.json to use dist/extension.js for desktop and dist/extension.web.js for web

Resolves web worker postMessage cloning errors while maintaining debugging capabilities.
chore: consolidate configuration change listeners and add initial configuration support

- Remove duplicate registerConfigurationChangeListener function from language-server.ts
- Use centralized configuration listener from configuration.ts
- Add sendInitialConfiguration function for startup configuration
- Fix configuration section references (remove non-existent 'apex' section)
- Update imports and exports for consolidated configuration management
- Add proper logging for configuration changes and initial setup
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

Successfully merging this pull request may close these issues.

2 participants