6.3.2: small fixes to typings

What's Changed

• fix Modal typings by @Ziemniakoss in #131
• Bugfix/add required attribute to input by @Ziemniakoss in #132

Full Changelog: v6.3.1...v6.3.2

6.3.1: Small fixes to event typings

added never as generic type parameter to ensure that some versions of VS Code detect event types correctly

v6.3.0

Fixes to typings for

• ShowToastEvent fixes (missing messageData parameter)
• navigate function (second parameter support
• getLoginLink and getLogoutLink support
• lightning/flow support

6.2.0: Apex typings improvements + checkout page support

• feature: support for apex subtypes
• feature: support for checkout page type reference
• bugfix: removed "," separating inner classes declarations

6.1.0: Clean command

Command for removing folders that contain only jsconfig.json file

6.0.2: We need to go deeper

• deeper schema (up to 5 levels deep)
• performance optimization using metadata caching
• more config options (see more info in project's wiki)

5.1.0 voice toolkit and bugfixes

What's Changed

• fix message service typings by
• make record type and record type id fields nullable
• support for voice toolkit api

Full Changelog: v5.0.6...v5.1.0

5.0.6 Fix lookup types

• now lookup fields that hold id of sobject have type apex.Id
• if field has helptext, it will be displayed in jsDocs for given field

5.0.3: Bugfixes after changes to apex parsing

Some fixes to apex typings generation, mainly:

• deleted some code that had no effect other than causing null pointers
• added better error handling

5.0.0: New parser

In this release I changed parser from my custom parser to one that works.
Thanks to this switch:

• we are using more stable parser that is "battle tested" by me during development of my Apex Language Server(currently closed source) and is considered to be included in PMD project so there is greater chance that it will be actively maintained in the future
• no compiled WASM in repository
• better typescript support (and it has documentation unlike parsers generated by tree-sitter (or maybe I just don't know how to use tree-sitter))
• we can bring back testing because tests won't need to be rewritten on every parser rewrite