Merge pull request #35 from leandrosimoes/fix/no-tree-view-found-error

Fix/no tree view found error

.codacy.yml

@@ -1,6 +1,5 @@
----
-exclude_paths:
-  - '.github/**'
-  - '.vscode/**'
-  - 'example/**'
-  - '**.md'
+exclude_paths:
+  - '.github/**'
+  - '.vscode/**'
+  - 'docs/**'
+  - '**.md'

.eslintrc

@@ -2,23 +2,20 @@
     "root": true,
     "globals": {
         "ko": true,
-        "window": true,
         "acquireVsCodeApi": true
     },
-    "extends": [
-        "defaults",
-        "airbnb-typescript-prettier",
-        "prettier"
-    ],
+    "env": {
+      "browser": true,
+      "es2021": true
+    },
+    "extends": ["eslint:recommended", "plugin:@typescript-eslint/recommended", "prettier"],
     "parser": "@typescript-eslint/parser",
     "parserOptions": {
-        "ecmaVersion": 6,
-        "sourceType": "module"
+        "ecmaVersion": 12,
+        "sourceType": "module",
+        "project": ["./tsconfig.json"]
     },
-    "plugins": [
-      "prettier",
-      "@typescript-eslint"
-    ],
+    "plugins": ["@typescript-eslint"],
     "rules": {
         "new-cap": "warn",
         "radix": 0,
@@ -77,15 +74,6 @@
                 "selector": "typeParameter", "format": ["PascalCase"], "prefix": ["T"] 
             }
         ],
-        "@typescript-eslint/no-empty-function": 0,
-        "prettier/prettier": [
-            "error",
-            {
-                "trailingComma": "es5",
-                "singleQuote": true,
-                "printWidth": 100,
-                "endOfLine": "auto"
-            }
-        ]
+        "@typescript-eslint/no-empty-function": 0
     }
 }

.github/FUNDING.yml

@@ -0,0 +1,2 @@
+github: leandrosimoes
+custom: ["https://www.buymeacoffee.com/leandrosimoes", lesimoes.dev]

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -0,0 +1,56 @@
+name: 🐞 Bug
+description: File a bug/issue
+title: "🐞 [BUG] <title>"
+labels: [bug]
+body:
+- type: checkboxes
+  attributes:
+    label: Is there an existing issue for this?
+    description: Please search to see if an issue already exists for the bug you encountered.
+    options:
+    - label: I have searched the existing issues
+      required: true
+- type: textarea
+  attributes:
+    label: Current Behavior
+    description: A concise description of what you're experiencing.
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Expected Behavior
+    description: A concise description of what you expected to happen.
+  validations:
+    required: false
+- type: textarea
+  attributes:
+    label: Steps To Reproduce
+    description: Steps to reproduce the behavior.
+    placeholder: |
+      1. In this environment...
+      2. With this config...
+      3. Run '...'
+      4. See error...
+  validations:
+    required: false
+- type: input
+  attributes:
+    label: Extension version that you are testing
+    description: E.g. v9.9.9
+  validations:
+    required: true
+- type: input
+  attributes:
+    label: OS
+    description: E.g. Windows, Mac OS, Linux...
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Anything else?
+    description: |
+      Links? References? Anything that will give us more context about the issue you are encountering!
+
+      Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
+  validations:
+    required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/feature_request.yaml

@@ -0,0 +1,20 @@
+name: ✨ Feature
+description: Suggest an idea for this project
+title: "✨ [FEATURE] <title>"
+labels: [enhancement]
+body:
+- type: textarea
+  attributes:
+    label: Describe what the feature is about?
+    description: A concise description of what you expected about the new feature.
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Anything else?
+    description: |
+      Links? References? Anything that will give us more context about the new feature requested!
+
+      Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
+  validations:
+    required: false

.vscode/settings.json

@@ -7,5 +7,10 @@
         "out": true // set this to false to include "out" folder in search results
     },
     // Turn off tsc task auto detection since we have the necessary tasks as npm scripts
-    "typescript.tsc.autoDetect": "off"
+    "typescript.tsc.autoDetect": "off",
+    "typescript.tsdk": "./node_modules/typescript/lib",
+    "editor.formatOnSave": false,
+    "editor.codeActionsOnSave": {
+        "source.fixAll.eslint": true
+    },
 }

CHANGELOG.md

@@ -8,12 +8,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [Unreleased]
 - You can see more about what's going on [here](https://github.com/leandrosimoes/project-urls-manager-vscode-extension/issues), even open a new issue with your sugestions/errors.
 
+## [1.2.3]
+- Fixed issue on open the side tree view
 
 ## [1.2.2]
 ### Changes
 - Add `package-lock.json` and `yarn.lock` files to be ignored into the default `ignorePaths` settings
 
-
 ## [1.2.1]
 ### Fixes
 - Fixed error on getting URLs on Mac OS

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to make participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers 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, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when
+an individual is representing the project or its community in public spaces.
+Examples of representing a project or community include using an official
+project e-mail address, posting via an official social media account, or acting
+as an appointed representative at an online or offline event. Representation of
+a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at <[email protected]>. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## 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/
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,28 @@
+# Contributing to Project URLs Manager VS Code Extension
+
+Thank you for your interest in contributing to Project URLs Manager VS Code Extension! See bellow how you can contribute with this project:
+
+## Issues
+
+All issues are valid since follow this simple rules:
+
+1) Check if there's any other issue open or close that matches your need/problem before open;
+2) Always follow the issue templates provided on open a new issue and answer the questions carefully;
+3) Always help to find the a solution. Don't be that guy that opens an issue and waits for the solution to come from others;
+4) Be kind with everyone;
+
+## Pull Requests
+
+Fell free to open a PR with your modifications, but keep in mind that it will be merged only if all the following rules are properly applied.
+
+1) The codes follow all the code standards. You can execute `yarn lint` to check if is everything fine before send your PR;
+2) You code was properly tested in real devices and everything works fine;
+3) You PR was reviewed and approved by the repository maintainers;
+
+## Donating
+
+If this repository helped you in any aspect, consider to send a donation to the repository owner:
+
+* [GitHub Sponsor Page](https://github.com/sponsors/leandrosimoes)
+* [Buy Me A Coffee](https://www.buymeacoffee.com/leandrosimoes)
+* [More Info](https://lesimoes.dev)

README.md

@@ -4,32 +4,32 @@
 
 # Project URLs Manager
 
-VS Code Extension to manage all urls found inside the workspace files
+VS Code Extension to manage all URLs found inside the workspace files
 
 ## Features
 
-This is how the Project URLs Manager looks like when open:
+This is what the Project URLs Manager looks like when open:
 
 ![URLs Manager](https://raw.githubusercontent.com/leandrosimoes/project-urls-manager-vscode-extension/master/docs/manager.png)
 
-* **Search Input**: Search for URLs on list
+* **Search Input**: Input Search for URLs on the list
 * **Ignored URLs Visibility Toggle** Toggle whenever you want to see or not the ignored URLs on the list
 * **URL Actions**: Copy to Clipboard, Ignore, Restore, Star and Unstar actions
 * **Ignored URL**: When ignored URLs are visible, they get a little bit of opacity
 * **URL Address**: Click at the URL address to open on your browser
-* **URL Description**: Add a quick description about the URL
-* **Status Bar/Open Button**: See how many URLs was found on your project and click to open the manager window
-* **Treview**: Pannels that shows all URLs separated by status. You can double click them to open on browser.
+* **URL Description**: Add a quick description of the URL
+* **Status Bar/Open Button**: See how many URLs were found on your project and click to open the manager window
+* **Treview**: Pannels that shows all URLs separated by status. You can double-click them to open on the browser.
 
 ## Extension Settings
 
 Manage the extension settings
 
 ![Settings UI](https://raw.githubusercontent.com/leandrosimoes/project-urls-manager-vscode-extension/master/docs/settings-ui.png)
 
-1. Comma separated of valid file extensions to be considered on sync. (E.g. `'.js,.css,.html'`)
-2. Comma separated domains to be ignored on sync. (E.g. `'google.con,facebook.com'`)
-3. Comma separated paths to be ignored on sync. (E.g. `'node_modules,src/your-file.js'`)
+1. A comma-separated string of valid file extension types that should be considered on sync. (E.g. `'.js,.css,.html'`)
+2. A comma-separated string of domains to be ignored on sync. (E.g. `'google.con,facebook.com'`)
+3. A comma-separated string of paths to be ignored on sync. (E.g. `'node_modules,src/your-file.js'`)
 
 The extension settings on VS Code JSON settings file are:
 
@@ -39,11 +39,11 @@ The extension settings on VS Code JSON settings file are:
 
 ## Commands
 
-There's some commands available for the extension too:
+There are some commands available for the extension too:
 
 ![Settings UI](https://raw.githubusercontent.com/leandrosimoes/project-urls-manager-vscode-extension/master/docs/commands.png)
 
-1. This command is used just by treeview, so if you execute it nothing is gonna happend
+1. This command is used just by tree view, so if you execute it nothing is gonna happen
 2. Show Project URLs Manager TreeView List
 3. Show Project URLs Manager TreeView List and focus on Ignored pannel
 4. Search for URLs in all files, respecting the `ignorePaths`, `ignoreDomains` and `extensionsList` provided configurations
@@ -54,4 +54,4 @@ There's some commands available for the extension too:
 
 ## Release Notes
 
-You can see all change log [here](https://github.com/leandrosimoes/project-urls-manager-vscode-extension/blob/develop/CHANGELOG.md).
+You can see all change logs [here](https://github.com/leandrosimoes/project-urls-manager-vscode-extension/blob/develop/CHANGELOG.md).