All notable changes to the "Hinty" extension will be documented in this file.
Check Keep a Changelog for recommendations on how to structure this file.
- Second Readme rewrite
- Removed unnecessary images
- Added GIF illustration
- Added logo to Readme
- 116 web development hints (omg!)
- After two years of usage and reaching almost 2k developers worldwide extension proved to be stable. That's why it's getting 1.0.0 version
- Narrowed rulesets to specific file extensions to improve performance. E.g. TypeScript rules are only checked against TypeScript files ("fileRegex": ".*\.ts")
- Renamed rulesets to .json for syntax checking and color highlighting
- Reorganized rulesets
- Grouped webdev rules into webdev.json for convenience (JavaScript, TypeScript, CSS, SCSS, Angular, React). Since rulesets can narrow filenames, it's ok to copy all rules, because it won't hinder performance. SQL is separately because idk what extensions should it handle
- Rewritten Readme.md file with Regex cheat-sheet and more
- New logo
- Rebranding to "Hinty". Linter -> Hinter -> Hinty
- Hinty brand hero
- Now rules can have fileRegex property that indicates what files should the rule be tested against
- New rules. Reached 50 rules.
- Article with SQL rules
- Information how to become a patron
- Added support of multiline regex (modifiers: 's')
- Performance improvement
- New rules for Angular
- First rules for CSS (SCSS) and JS. Also a general rule
- Unit tests
- Rulesets: Added file with rulesets, and rule-set for Angular
- Readme: Minor updates
- Readme: Link to rule-set for Angular/TypeScript
- Readme: Added comparison to regular Linters and SonarLint
- Readme: Added instruction how to add rules to user settings
- Now you can set up RegEx modifiers for rules and globally for workspace eg. 'gi' for case insensitive rules
- Autocomplete will help you write Hinty rules and indicate spelling mistakes
- Instruction for the extension is clearer
- Notes does not show up in configuration file anymore
- Performance improvement
- Initial release