Skip to content

Commit eca775a

Browse files
authored
Merge pull request #1 from mrjonleek/main
Ownership and repository change.
2 parents 8a76cf1 + 4f18e60 commit eca775a

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

66 files changed

+9063
-1
lines changed

.eslintrc.json

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
{
2+
"root": true,
3+
"parser": "@typescript-eslint/parser",
4+
"parserOptions": {
5+
"ecmaVersion": 6,
6+
"sourceType": "module"
7+
},
8+
"plugins": [
9+
"@typescript-eslint"
10+
],
11+
"rules": {
12+
"@typescript-eslint/naming-convention": [
13+
"warn",
14+
{
15+
"selector": "import",
16+
"format": [ "camelCase", "PascalCase" ]
17+
}
18+
],
19+
"@typescript-eslint/semi": "warn",
20+
"curly": "warn",
21+
"eqeqeq": "warn",
22+
"no-throw-literal": "warn",
23+
"semi": "off"
24+
},
25+
"ignorePatterns": [
26+
"out",
27+
"dist",
28+
"**/*.d.ts"
29+
]
30+
}

.gitignore

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
out
2+
dist
3+
node_modules
4+
.vscode-test/
5+
*.vsix

.vscode-test.mjs

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
import { defineConfig } from '@vscode/test-cli';
2+
3+
export default defineConfig({
4+
files: 'out/test/**/*.test.js',
5+
});

.vscode/extensions.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
{
2+
// See http://go.microsoft.com/fwlink/?LinkId=827846
3+
// for the documentation about the extensions.json format
4+
"recommendations": ["dbaeumer.vscode-eslint", "amodio.tsl-problem-matcher", "ms-vscode.extension-test-runner"]
5+
}

.vscode/launch.json

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
// A launch configuration that compiles the extension and then opens it inside a new window
2+
// Use IntelliSense to learn about possible attributes.
3+
// Hover to view descriptions of existing attributes.
4+
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
5+
{
6+
"version": "0.2.0",
7+
"configurations": [
8+
{
9+
"name": "Run Extension",
10+
"type": "extensionHost",
11+
"request": "launch",
12+
"args": [
13+
"--extensionDevelopmentPath=${workspaceFolder}"
14+
],
15+
"outFiles": [
16+
"${workspaceFolder}/dist/**/*.js"
17+
],
18+
"preLaunchTask": "${defaultBuildTask}"
19+
}
20+
]
21+
}

.vscode/settings.json

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
// Place your settings in this file to overwrite default and user settings.
2+
{
3+
"files.exclude": {
4+
"out": false, // set this to true to hide the "out" folder with the compiled JS files
5+
"dist": false // set this to true to hide the "dist" folder with the compiled JS files
6+
},
7+
"search.exclude": {
8+
"out": true, // set this to false to include "out" folder in search results
9+
"dist": true // set this to false to include "dist" folder in search results
10+
},
11+
// Turn off tsc task auto detection since we have the necessary tasks as npm scripts
12+
"typescript.tsc.autoDetect": "off"
13+
}

.vscode/tasks.json

Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
// See https://go.microsoft.com/fwlink/?LinkId=733558
2+
// for the documentation about the tasks.json format
3+
{
4+
"version": "2.0.0",
5+
"tasks": [
6+
{
7+
"type": "npm",
8+
"script": "watch",
9+
"problemMatcher": "$ts-webpack-watch",
10+
"isBackground": true,
11+
"presentation": {
12+
"reveal": "never",
13+
"group": "watchers"
14+
},
15+
"group": {
16+
"kind": "build",
17+
"isDefault": true
18+
}
19+
},
20+
{
21+
"type": "npm",
22+
"script": "watch-tests",
23+
"problemMatcher": "$tsc-watch",
24+
"isBackground": true,
25+
"presentation": {
26+
"reveal": "never",
27+
"group": "watchers"
28+
},
29+
"group": "build"
30+
},
31+
{
32+
"label": "tasks: watch-tests",
33+
"dependsOn": [
34+
"npm: watch",
35+
"npm: watch-tests"
36+
],
37+
"problemMatcher": []
38+
}
39+
]
40+
}

.vscodeignore

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
.vscode/**
2+
.vscode-test/**
3+
out/**
4+
node_modules/**
5+
src/**
6+
.gitignore
7+
.yarnrc
8+
webpack.config.js
9+
vsc-extension-quickstart.md
10+
**/tsconfig.json
11+
**/.eslintrc.json
12+
**/*.map
13+
**/*.ts
14+
**/.vscode-test.*

CHANGELOG.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
# Change Log
2+
3+
All notable changes to the "open-gis-editor" extension will be documented in this file.
4+
5+
Check [Keep a Changelog](http://keepachangelog.com/) for recommendations on how to structure this file.
6+
7+
## [Unreleased]
8+
9+
- Initial release

README.md

Lines changed: 97 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,97 @@
1-
# vscode-extension
1+
# Open GIS Editor
2+
https://www.flaticon.com/free-icon/topography_992325?related_id=992325&origin=search
3+
<a href="https://www.flaticon.com/free-icons/topography" title="topography icons">Topography icons created by geotatah - Flaticon</a>
4+
https://github.com/microsoft/vscode-webview-ui-toolkit
5+
6+
A VSCode extension based on the [Open GIS IDE] for working with geospactial data.
7+
8+
This is the README for your extension "open-gis-editor". After writing up a brief description, we recommend including the following sections.
9+
10+
## Coordinate Reference System (CRS)
11+
- https://epsg.io
12+
- https://en.wikipedia.org/wiki/List_of_national_coordinate_reference_systems
13+
- https://mapserver.org/ogc/wms_server.html#coordinate-systems-and-axis-orientation
14+
15+
16+
## LatLong ranges
17+
18+
North (+90)
19+
|
20+
(-180) West ———+——— East (+180)
21+
|
22+
South (-90)
23+
24+
## Features
25+
26+
Describe specific features of your extension including screenshots of your extension in action. Image paths are relative to this README file.
27+
28+
For example if there is an image subfolder under your extension project workspace:
29+
30+
\!\[feature X\]\(images/feature-x.png\)
31+
32+
> Tip: Many popular extensions utilize animations. This is an excellent way to show off your extension! We recommend short, focused animations that are easy to follow.
33+
34+
## Functionality
35+
- Neatify: format document to be neatly organized by a subset of linear properties like Features to a FeatureCollection.
36+
- Preffify: format document to be easily traversible (collaapsable) for human interactivty.
37+
- Minify: compress document whitespace for maximum size optimization.
38+
39+
## Requirements
40+
41+
Persist state or reconstitude document map https://code.visualstudio.com/api/extension-guides/webview#persistence
42+
43+
If you have any requirements or dependencies, add a section describing those and how to install and configure them.
44+
45+
## Extension Settings
46+
47+
Include if your extension adds any VS Code settings through the `contributes.configuration` extension point.
48+
49+
For example:
50+
51+
This extension contributes the following settings:
52+
53+
* `myExtension.enable`: Enable/disable this extension.
54+
* `myExtension.thing`: Set to `blah` to do something.
55+
56+
## Known Issues
57+
58+
Calling out known issues can help limit users opening duplicate issues against your extension.
59+
60+
## Release Notes
61+
62+
Users appreciate release notes as you update your extension.
63+
64+
### 1.0.0
65+
66+
Initial release of ...
67+
68+
### 1.0.1
69+
70+
Fixed issue #.
71+
72+
### 1.1.0
73+
74+
Added features X, Y, and Z.
75+
76+
---
77+
78+
## Following extension guidelines
79+
80+
Ensure that you've read through the extensions guidelines and follow the best practices for creating your extension.
81+
82+
* [Extension Guidelines](https://code.visualstudio.com/api/references/extension-guidelines)
83+
84+
## Working with Markdown
85+
86+
You can author your README using Visual Studio Code. Here are some useful editor keyboard shortcuts:
87+
88+
* Split the editor (`Cmd+\` on macOS or `Ctrl+\` on Windows and Linux).
89+
* Toggle preview (`Shift+Cmd+V` on macOS or `Shift+Ctrl+V` on Windows and Linux).
90+
* Press `Ctrl+Space` (Windows, Linux, macOS) to see a list of Markdown snippets.
91+
92+
## For more information
93+
94+
* [Visual Studio Code's Markdown Support](http://code.visualstudio.com/docs/languages/markdown)
95+
* [Markdown Syntax Reference](https://help.github.com/articles/markdown-basics/)
96+
97+
**Enjoy!**

0 commit comments

Comments
 (0)