- Hover provider showing entity information and type - Go-to-definition (F12) for entity references - Basic IFC file validation (ISO-10303-21 header check) - Entity parsing with regex-based detection - Proper CommonJS module system (avoiding ES module issues) This replaces the broken baseline from ifc-developer-tools which had: - Non-functional ES module configuration - Circular dependency issues - Parser crashes - Non-working PositionVisitor Built on Microsoft's LSP example template for a clean, maintainable foundation. Next: Add hierarchical entity dependency tree in hover tooltip."
961 B
961 B
How to Contribute
Pull Requests
We also accept [pull requests][pull-request]!
Generally we like to see pull requests that
- Maintain the existing code style
- Are focused on a single change (i.e. avoid large refactoring or style adjustments in untouched code if not the primary goal of the pull request)
- Have good commit messages
- Have tests
- Don't decrease the current code coverage (see coverage/lcov-report/index.html)
Building
yarn
yarn test
Running yarn test -- dev will watch for tests within Node and karma start may be used for manual testing in browsers.
If you notice any problems, please report them to the GitHub issue tracker at http://github.com/kpdecker/jsdiff/issues.
Releasing
A full release may be completed with the following:
yarn clean
yarn grunt
yarn grunt uglify
yarn publish