initial commit

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,43 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: 'bug'
+assignees: ''
+
+---
+
+## Checklist before submitting a bug report
+
+- [ ] I have reviewed [CONTRIBUTING.md](https://github.com/opencaesar/oml-vision/blob/master/CONTRIBUTING.md) document
+- [ ] I have done a quick search on the issue tracker to check if the bug report is not redundant
+
+## Context
+
+[Give a concise summary of the bug that you have encountered]
+
+## Steps to reproduce the bug
+
+[List of the steps to reproduce the bug. If relevant, you may add SysMLv2 or KerML code snippets or files that exhibit the bug.]
+
+## Current result
+
+[What currently happens]
+
+## Expected result
+
+[What is expected to happen instead]
+
+## Additional context
+
+[Any additional context. If applicable, you may provide screenshots and/or error logs.]
+
+## Possible fix
+
+[Not required but you can suggest possible fixes for the bug or link a place in the code that could possibly be causing the bug]
+
+## Technical data
+
+- Operating system: [What is the OS]
+- Version of the repo: [What is the release version or a commit of the repo]
+- VSCode version: [What is the VSCode version]

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,25 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: 'feature'
+assignees: ''
+
+---
+
+## Checklist before submitting a feature request
+
+- [ ] I have reviewed [CONTRIBUTING.md](https://github.com/opencaesar/oml-vision/blob/master/CONTRIBUTING.md) document
+- [ ] I have done a quick search on the issue tracker to check if the feature request is not redundant
+
+## Is your feature request related to a problem? If yes, describe the problem
+
+[If your feature is related to some problem, please describe it. E.g. _I am annoyed that whenever I do X, I need to..._ ]
+
+## Describe the desired feature
+
+[Clearly and concisely describe the functionality that you would like to see]
+
+## Additional context
+
+[Any additional context]

.github/pull_request_template.md

@@ -0,0 +1,24 @@
+## Checklist before submitting a merge request
+
+- [ ] I have reviewed [CONTRIBUTING.md](https://github.com/opencaesar/oml-vision/blob/master/CONTRIBUTING.md) document
+- [ ] All commits have been signed-off for the Developer Certificate of Origin. See [here](https://github.com/opencaesar/oml-vision/blob/master/CONTRIBUTING.md#developer-certificate-of-origin).
+- [ ] I have added my contribution to [CHANGELOG.md](https://github.com/opencaesar/oml-vision/blob/master/CHANGELOG.md)
+
+## Description of contribution
+
+[Describe your contribution, link to any existing relevant issues]
+
+## Testing performed
+
+<!-- If needed, describe additional testing that was performed for any changes -->
+
+- [ ] I have added unit tests to cover additional functionality
+
+
+## Expected functionality changes
+
+[Describe expected behaviour changes]
+
+## Additional context
+
+[If needed, you may add additional context]

.gitignore

@@ -0,0 +1,20 @@
+# Dependencies
+/node_modules
+
+# Production
+/build
+
+# Generated files
+.docusaurus
+.cache-loader
+
+# Misc
+.DS_Store
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*

.stackblitzrc

@@ -0,0 +1,4 @@
+{
+  "installDependencies": true,
+  "startCommand": "npm start"
+}

CHANGELOG.md

@@ -0,0 +1,18 @@
+# Change Log
+
+All notable changes to the "oml-vision" extension will be documented in this file.
+
+Check [Keep a Changelog](http://keepachangelog.com/) for recommendations on how to structure this file.
+
+## [0.2.0]
+
+### Fixed
+- Tree View shows VSCode error popup with Tree UI bugs https://github.com/opencaesar/oml-vision/pull/5
+
+### Added
+- Add export to SVG for diagrams https://github.com/opencaesar/oml-vision/pull/3
+
+## [0.1.0]
+
+### Added
+- Initial release

CODE_OF_CONDUCT.md

@@ -0,0 +1,131 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at (see contact links): https://www.opencaesar.io/contributors/
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

CONTRIBUTING.md

@@ -0,0 +1,50 @@
+# How to contribute
+
+We thank you for taking time to contribute! We appreciate your help with feature implementation, bug fixes, unit tests, or just for reporting the issues and improvement ideas.
+
+- Developer instructions are available in the [DEVELOPMENT.md](DEVELOPMENT.md)
+- Project's main issue tracker is [here](https://github.com/opencaesar/oml-vision/issues/new/choose) and this is the prefered place to post issues. 
+- Free free to contact the maintainers of the project [here](https://www.opencaesar.io/contributors/)
+
+## Environment details
+
+Details on how to build and set up the project are available in the [README.md](README.md#developer-instructions).
+
+## Testing
+
+We use [Jest](https://jestjs.io/) for unit testing. We would always be happy to increase unit test coverage. Please write unit tests for new code that you create.
+
+## Reporting bugs
+
+You may report bugs to the issue tracker [here](https://github.com/opencaesar/oml-vision/issues/new/choose). 
+
+## Suggesting features
+
+You may post feature/enhancement requests on the project's issue tracker [here](https://github.com/opencaesar/oml-vision/issues/new/choose).
+
+## Coding conventions
+
+We suggest using Google's TypeScript coding conventions found [here](https://google.github.io/styleguide/tsguide.html).
+
+## Submitting changes
+
+Please create a pull request to our project's Github repo. As a merge request description, please fill in the pull request description template [here](https://github.com/opencaesar/oml-vision/pulls). We would be very grateful if you would include Jest unit tests for the added code.
+
+Make sure that all of your commits are atomic (i.e. addressing not more than one feature per commit) and always write a clear message for your commits.
+
+For branch names, use convention `fix/ISSUE_NUMBER-<FIX_SUMMARY>` for bug fixes and `feat/ISSUE_NUMBER-<FEAT_SUMMARY>` for feature implementations.
+
+### Developer certificate of origin
+
+Contributions to this repository are subject to the [Developer Certificate of Origin](DCO). All commits should be signed off by either using `-s` or `--signed` flag while committing:
+```
+git commit -s -m "My commit message"
+```
+
+Alternatively, you can add additional line to the commit message:
+
+```
+My commit message
+
+Signed-off-by: Dev McDeveloper <[email protected]>
+```

DCO

@@ -0,0 +1,37 @@
+Developer Certificate of Origin
+Version 1.1
+
+Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
+1 Letterman Drive
+Suite D4700
+San Francisco, CA, 94129
+
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
+
+
+Developer's Certificate of Origin 1.1
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I
+    have the right to submit it under the open source license
+    indicated in the file; or
+
+(b) The contribution is based upon previous work that, to the best
+    of my knowledge, is covered under an appropriate open source
+    license and I have the right under that license to submit that
+    work with modifications, whether created in whole or in part
+    by me, under the same open source license (unless I am
+    permitted to submit under a different license), as indicated
+    in the file; or
+
+(c) The contribution was provided directly to me by some other
+    person who certified (a), (b) or (c) and I have not modified
+    it.
+
+(d) I understand and agree that this project and the contribution
+    are public and that a record of the contribution (including all
+    personal information I submit with it, including my sign-off) is
+    maintained indefinitely and may be redistributed consistent with
+    this project or the open source license(s) involved.