Fix default `source.path` bug

What's Changed

• fix: default source path bug by @no-stack-dub-sack in #81

Full Changelog: v2.0.2...v2.0.3

Credits

Thanks @pbornath for identifying this issue and raising #80.

Fix handling of empty path settings

What's Changed

• fix: return better default in resolveWorkspaceFolder in order to handle empty path settings (e.g. homePagePath, see #78) by @no-stack-dub-sack in #79

Full Changelog: v2.0.1...v2.0.2

Fix "ApexDox: Open Docs" bug

What's Changed

• fix: open docs bug by @no-stack-dub-sack in #77

Full Changelog: v2.0.0...v2.0.1

2.0.0 Release

Breaking Changes

Technically, v1.6.0 should have been a major release, as breaking changes were inadvertently introduced in that version. With the introduction of #68, previously excluded files living in subdirectories of directories explicitly referenced source.path config would now be included. To exclude subdirectories, use the exclude configuration setting. Excluding files seemed less common than wanting to include sub-dirs implicitly, so this seemed like a fair trade-off. This release also fixes a bug in the initial implementation of #68 which caused links to classes and methods in doc files to break.

What's Changed

• chore(deps): bump y18n from 4.0.0 to 4.0.3 by @dependabot in #72
• fix: source links post-recursive file discovery update by @no-stack-dub-sack in #74
• fix: vscode version, info messages, update docs by @no-stack-dub-sack in #75

Full Changelog: v1.6.0...v2.0.0

Fix Bug With Recursive Class File Discovery

This is a non-prod ready pre-release for testing only and will not be published to the vscode marketplace until prod-ready.

Various updates & improvements

EDIT: This release inadvertently included breaking changes with the introduction of #68. Please see the 2.0.0 release for details.

This release includes the following improvements and features (and noting an interesting theme of PR numbers that made it into this release!):

• Updates HighlightJS to v11 and improves support for Apex highlighting and other languages. Thanks to @dschach for his work on PR #48 for this update.
• Improves support for HTML tags in documentation comments (adds support for b, strong, i, em, s, u, ol, ul, and li tags). Thanks to @cemerson for his work on this feature in PR #58.
• Improves .cls file discoverability by recursively scanning source directories, reducing the number of explicit directories users have to define in their configs for projects with nested folder structures. Thanks to @codefriar for his work on this feature in PR #68.

Improve @author and @since support

Improves use of @author and @since tags so that multiple of each tag can be used to form something of a changelog. Previously, multiple instances of these tags were just blindly concatenated. Thanks to @docbill for his work on this feature, found in #55;

Fix HTML Generation Issues, Security Updates

This release fixes two bugs identified by @dschach:

• Fixes h2/h3 tag mismatch issue found in PropertyMarkupGenerator and ChildEnumMarkupGenerator
• Fixes issue where whitespace / newlines found in code examples in user-provided HTML content (such as homepages and other files provided the the pages setting) was not being preserved, resulting in unformatted code.
• Thanks @dschach for the bug report and the PR!

This release also includes several dependabot security vulnerability updates.

Deprecate @returns in favor of @return

This release deprecates the non-standard/JSDoc style @returns token in favor of JavaDoc style @return token. Thanks to @berardo for the contribution.

NOTE that this should have been version 1.1.0, however the vsce publish minor command bumps the version regardless of whether or not the operation succeeds. Due to connectivity issues, this command failed a few times before succeeding and I did not realize the version had already been bumped. In other words, versions 1.1.x through 1.3.x were skipped / never existed.

Fix "ApexDox: Run" bug introduced in VS Code 1.41.1

This release fixes a bug reported by @dmitry-prohorov in #12 and updates the way unknown config settings are handled by the extension.