@codingame/monaco-editor-wrapper 5.3.2 → 5.4.0-full-workbench.1

package/dist/assets/castwide.solargraph-0.24.1.vsix/README.md

@@ -0,0 +1,178 @@
+# VS Code Solargraph Extension
+
+Solargraph is a language server that provides intellisense, code completion, and inline documentation for Ruby.
+
+![Screenshot](https://github.com/castwide/vscode-solargraph/raw/HEAD/vscode-solargraph-0.34.1.gif)
+
+## Features
+
+* Context-aware suggestions and documentation for the Ruby core
+* Detection of some variable types and method return values (e.g., `String.new.` returns String instance methods)
+* Identification of local, class, and instance variables within the current scope
+* Find references and rename symbols (experimental as of solargraph gem v0.22.0)
+* Support for gems
+* Near-complete support for the Ruby core and stdlib
+* Partial support for Ruby on Rails
+
+## Requirements
+
+You need to install the Ruby gem:
+
+    gem install solargraph
+
+## Usage
+
+### Code Completion
+
+Open a Ruby file and start typing. Solargraph should start providing contextual code suggestions. To start a search manually, hit ctrl-space. Example:
+
+    Stri # <- Hitting ctrl-space here will suggest String
+
+Method arguments and documentation can be seen by starting parentheses after the method call. Example:
+
+    String.new.casecmp( # <- Displays arguments and documentation for String#casecmp
+
+### Documentation
+
+Solargraph provides a command to access searchable documentation directly from the IDE.
+
+* Hit ctrl+shift+r (or hit ctrl+shift+p and find `Search Ruby Documentation`).
+* Enter a keyword or path to search; e.g., `String` or `Array#join`.
+
+The documentation includes the Ruby core, required gems, and the current workspace. Documentation from the workspace is automatically updated when you save the corresponding file.
+
+You can also hover over variables, constants, and method calls to see popup information with links to more documentation.
+
+#### Documenting Your Code
+
+Using [YARD](http://www.rubydoc.info/gems/yard/file/docs/GettingStarted.md) for inline documentation is highly recommended.
+Solargraph will use YARD comments to provide the best code completion and API reference it can.
+
+In addition to the standard YARD tags, Solargraph defines a `@type` tag for documenting variable types. It works with both
+local and instance variables. Example:
+
+    # @type [String]
+    my_variable = some_method_call
+    my_variable. # <= Hitting crtl-space here will suggest String instance methods
+
+### Intellisense
+
+Solargraph also provides hovers and go to definition.
+
+Hover your mouse over code to see method definitions, return values, and links to documentation.
+
+To go to a method or variable's definition, right-click and select "Go to Definition" from the context menu, or press F12 for the definition at the cursor.
+
+### Gem Support
+
+Solargraph is capable of providing code completion and documentation for gems. When your code uses `require` to include a gem, its classes and methods become available in completion and intellisense.
+
+You can make sure your gems are available with the commands `Build new gem documentation` or `Rebuild all gem documentation` in the command palette.
+
+### Solargraph and Bundler
+
+If your project uses Bundler, the most comprehensive way to use your bundled gems is to bundle Solargraph.
+
+In the Gemfile:
+
+    gem 'solargraph', group: :development
+
+Run `bundle install` and use `bundle exec yard gems` to generate the documentation. This process documents cached or vendored gems, or even gems that are installed from a local path.
+
+In order to access intellisense for bundled gems, you'll need to start the language server with Bundler by setting the `solargraph.useBundler` option to `true`.
+
+> Note: solargraph.bundlerPath should be an absolute path to bundler executable.
+
+### Diagnostics (Linting)
+
+To enable diagnostics, set the `solargraph.diagnostics` configuration to `true`.
+
+Solargraph uses RuboCop for diagnostics by default. If your project has a .solargraph.yml file, you can configure the diagnostics in its `reporters` section. Example:
+
+    reporters:
+    - rubocop
+
+See [the configuration guide](https://solargraph.org/guides/configuration) for more information about the .solargraph.yml file.
+
+Use a .rubocop.yml file in your project's root folder to customize the linting rules.
+
+### Restarting Solargraph
+
+Some changes you make to a project, such as updating the Gemfile, might require you to restart the Solargraph server.
+Instead of reloading the VS Code window, you can run Restart Solargraph from the Command Palette.
+
+### Project Configuration
+
+Solargraph will use the .solargraph.yml file for configuration if it exists in the workspace root. The extension provides
+a command to `Create a Solargraph config file`, or you can do it from the command line:
+
+    $ solargraph config .
+
+The default file should look something like this:
+
+    include:
+      - ./**/*.rb
+    exclude:
+      - spec/**/*
+
+This configuration tells Solargraph to parse all .rb files in the workspace excluding the spec folder.
+
+## Updating the Core Documentation
+
+The Solargraph gem ships with documentation for Ruby 2.2.2. As of gem version 0.15.0, there's an option to download additional documentation for other Ruby versions from the command line.
+
+    $ solargraph list-cores      # List the installed documentation versions
+    $ solargraph available-cores # List the versions available for download
+    $ solargraph download-core   # Install the best match for your Ruby version
+    $ solargraph clear-cores     # Clear the documentation cache
+
+## Extension Settings
+
+This extension contributes the following settings:
+
+* `solargraph.commandPath`: Path to the solargraph command.  Set this to an absolute path to select from multiple installed Ruby versions.
+* `solargraph.useBundler`: Use `bundle exec` to run solargraph. (If this is true, `solargraph.commandPath` is ignored.)
+* `solargraph.bundlerPath`: Path to the bundle command.
+* `solargraph.checkGemVersion`: Check if a new version of the Solargraph gem is available. Default is true (recommended).
+* `solargraph.diagnostics`: Enable diagnostics reporting. See [the configuration guide](https://solargraph.org/guides/configuration) for diagnostics options.
+* `solargraph.completion`: Enable autocompletion.
+* `solargraph.hover`: Enable tips on hover.
+* `solargraph.autoformat`: Enable automatic formatting while typing.
+* `solargraph.formatting`: Enable document formatting. The gem currently uses RuboCop for formatting.
+* `solargraph.symbols`: Enable search for document and workspace symbols.
+* `solargraph.definitions`: Enable go-to-definition.
+* `solargraph.rename`: Enable symbol renaming.
+* `solargraph.references`: Enable finding references.
+* `solargraph.folding`: Enable folding ranges.
+* `solargraph.transport`: socket (default), stdio, or external. See [Transport Options](#transport-options) for more information.
+* `solargraph.externalServer`: The host and port for external transports. See [Transport Options](#transport-options) for more information.
+* `solargraph.logLevel`: The logging level. Options in ascending amount of detail are `warn`, `info`, and `debug`. The default is `warn`.
+
+## Transport Options
+
+Extension version 0.18.0 introduces the `solargraph.transport` setting with the following options:
+
+* `socket`: Run a TCP server. This is the default option.
+* `stdio`: Run a STDIO server.
+* `external`: Connect to an external server instead of starting a new one.
+
+Most users should use the default `socket` option or switch to `stdio` in case of network issues.
+
+The `external` option is intended for cases where the project is hosted in a different environment from the editor,
+such as a docker container or a remote server. Users can opt to run a socket server in the remote environment and connect
+to it via TCP. Example configuration:
+
+    "solargraph.transport": "external",
+    "solargraph.externalServer": {
+        "host": "localhost",
+        "port": 7658
+    }
+
+## More Information
+
+See the [Solargraph website](https://solargraph.org) for guides, tips, and updates.
+
+## Known Issues
+
+* Partial support for Rails (see [https://solargraph.org/guides/rails](https://solargraph.org/guides/rails))
+* Documentation pages need better design/layout

package/dist/assets/ckolkman.vscode-postgres-1.4.3.vsix/CHANGELOG.md

@@ -0,0 +1,232 @@
+# Change Log
+All notable changes to the "vscode-postgres" extension will be documented in this file.
+
+## [Unreleased]
+- Turn off parsing of pg types `date`, `timestamp`, and `timestamptz` for more consistent formatting. Should fix [#223](https://github.com/Borvik/vscode-postgres/issues/223) and [#219](https://github.com/Borvik/vscode-postgres/issues/219).
+- Removes keytar to SecretStorage API migration code and remove references to keytar. Fixes: [#230](https://github.com/Borvik/vscode-postgres/issues/230).
+
+## [1.4.2] - 2023-04-14
+- Fix for JSON export formatting. Fixes issue [#220](https://github.com/Borvik/vscode-postgres/issues/220)
+
+## [1.4.1] - 2023-04-08
+- Make intellisense ignore tables that have 0 columns - thanks @polmonso.
+- Fixed csv exporting of timestamps. Fixes issue [#114](https://github.com/Borvik/vscode-postgres/issues/114).
+- Added hex formatting for `bytea` columns - thanks @jragingfury.
+
+## [1.4.0] - 2022-01-19
+- Keytar migration tool. Previously, keytar was used manually via `${vscode.env.appRoot}/node_modules` - this is a switch to using the secrets api, but needed a migration to do so.
+
+## [1.3.0] - 2022-01-03 (prerelease)
+- Switch to pre-release/release version numbers `major.EVEN.patch` for release and `major.ODD.patch` for pre-release
+- Keytar migration tool. Previously, keytar was used manually via `${vscode.env.appRoot}/node_modules` - this is a switch to using the secrets api, but needed a migration to do so.
+
+## [1.1.19] - 2021-10-16
+### Added
+- Query timer and running message by Jakub Szostak
+
+### Updated
+- Updated webview URL creation for local files
+
+## [1.1.18] - 2021-06-12
+### Fixed
+- Webview results not displaying
+
+### Added
+- Sticky table headers
+
+## [1.1.17] - 2021-01-18
+### Fixed
+- Saving results to CSV, JSON, or XML when results have multiple columns with the same name - some columns were getting dropped (issue [#164](https://github.com/Borvik/vscode-postgres/issues/164))
+  Now all columns _should_ be output.  For the case of JSON or XML, repeated names have an increment suffix to the name. For CSV columns are positional
+  and it uses the same name.
+
+## [1.1.16] - 2021-01-18
+### Added
+- Foreign table support
+- Ability to copy schema, table, column, and function names to the clipboard
+
+### Changed
+- Select [x] right click options - moved to submenu with extra options
+
+## [1.1.15] - 2021-01-14
+### Fixed
+- Updated queries for breaking `has_schema_privilege` calls (issues [#161](https://github.com/Borvik/vscode-postgres/issues/161), [#129](https://github.com/Borvik/vscode-postgres/issues/129))
+- Query updates to allow for materialized views to show (issue [#112](https://github.com/Borvik/vscode-postgres/issues/112))
+
+## [1.1.14] - 2020-10-24
+### Fixed
+- Update `pg` caused SSL mode to break for self-signed certs (issue [#154](https://github.com/Borvik/vscode-postgres/issues/154)), added `rejectUnauthorized: false`
+
+## [1.1.13] - 2020-10-17
+### Fixed
+- Emergency update of dependencies
+
+## [1.1.12] - 2020-10-17
+### Fixed
+- `[DEP0005] DeprecationWarning: Buffer()` (issue [#147](https://github.com/Borvik/vscode-postgres/issues/147)) - thanks in large part to @alisabzevari
+
+## [1.1.11] - 2019-08-10
+### Fixed
+- Sidebar icon has been updated and should now size correctly for vscode 1.37.0.
+
+## [1.1.10] - 2019-04-12
+### Fixed
+- Add DB connection process now handles more issues with connecting to a possibly secured `postgres` database (issue [#97](https://github.com/Borvik/vscode-postgres/issues/97)).
+
+## [1.1.9] - 2019-03-17
+### Changed
+- Add DB connection process has been altered to be more user friendly. Also fixes ssl cert issues (issue [#66](https://github.com/Borvik/vscode-postgres/issues/66)).
+
+## [1.1.8] - 2019-03-08
+### Fixed
+- PG 11 Version issues for language server (issue [#92](https://github.com/Borvik/vscode-postgres/issues/92)).
+
+## [1.1.7] - 2019-03-05
+### Fixed
+- Delete results now properly show RETURNING data (issue [#91](https://github.com/Borvik/vscode-postgres/issues/91)).
+
+## [1.1.6] - 2018-11-26
+### Fixed
+- Syntax highlighting when first character of query is a space (issue [#79](https://github.com/Borvik/vscode-postgres/issues/79)) by @votagus.
+
+## [1.1.5] - 2018-11-26
+### Added
+- Capability to better separate main queries by pg version
+- Support for default connections using settings which can be overridden at the project level (issue [#69](https://github.com/Borvik/vscode-postgres/issues/69))
+  - To better support default connections, the extension now activates on start vs. when a view/language/command is accessed for the first time.
+
+### Fixed
+- Support of PG 11 in function explorer (issue [#72](https://github.com/Borvik/vscode-postgres/issues/72))
+
+## [1.1.4] - 2018-10-29
+### Added
+- `Functions` virtual folder (must enable in configuration) by @lafriks
+- Added schemas to autocompletion by @lafriks
+
+### Fixed
+- Better hiding of `pg_temp` and `pg_toast` tables by @lafriks
+
+## [1.1.3] - 2018-10-06
+### Added
+- Better support for blank passwords - doesn't touch Keytar (thanks to @SWW13)
+
+### Fixed
+- Performance opening table to show columns degraded when the column query when support was added for v9.3.  Version detection was put in to allow a better performing query to work on 9.4+.
+
+## [1.1.2] - 2018-09-24
+### Added
+- Support for PostgreSQL 9.3
+
+## [1.1.1] - 2018-09-10
+### Fixed
+- `prettyPrintJSONfields` setting should work again
+
+## [1.1.0] - 2018-09-03
+### Updated
+- Transitioned result pane from using TextDocumentContentProvider to using Webviews.
+
+### Fixed
+- Serialize results to JSON and XML should work properly again (broke with fix in 1.0.15).
+
+### Added
+- Support for `circle` and `point` geometric types.
+- All query results now use the result pane.
+
+## [1.0.16] - 2018-08-18
+### Fixed
+- Explain statements should now work again (broke with fix in 1.0.15)
+
+### Added
+- Icon for foreign keys in the database explorer.
+- Display formatted type names in results grid headers by @lnicola
+
+## [1.0.15] - 2018-08-16
+### Fixed
+- Display of results when running queries with multiple columns of the same name.
+
+## [1.0.14] - 2018-08-10
+### Fixed
+- Display of `interval` data formats
+- Changed using namespace name to oid for issue [#33](https://github.com/Borvik/vscode-postgres/issues/33)
+
+## [1.0.13] - 2018-07-18
+### Added
+- Support for optionally providing a database when creating a connection (ends up with a single-database connection in the db explorer).
+- Added configuration setting to control the sort order of table columns: database order, alphabetical, and reverse alpha.
+
+## [1.0.12] - 2018-07-14
+### Fixed
+- Quoted schemas/tables in priviledge queries.
+
+### Added
+- Support for editing connection details.
+
+## [1.0.11] - 2018-07-06
+### Fixed 
+- Preserve query focus code was spawning a new query editor.
+
+## [1.0.10] - 2018-07-06
+### Fixed 
+- Windows bug causing "cannot read property of null" errors - solved simultaneously with @Yarith
+
+## [1.0.9] - 2018-05-30
+### Fixed
+- Info/Error node - if an error occurred when expanding a node in the database explorer there wasn't an indication of what went wrong
+
+### Added
+- Support for PostgreSQL user permissions. Databases, schemas, tables, views should all be filtered based on the user used when setting up the connection.
+- Support for quoted identifiers
+
+## [1.0.8] - 2018-05-23
+### Added
+- Option to disable changing active connection when navigating the explorer by @mterring
+
+## [1.0.7] - 2018-05-16
+### Added
+- Schema support to table nodes and capitalized table names by @jgoday
+
+## [1.0.6] - 2018-05-12
+### Fixed
+- Code Completion: grouped fields of the same data type together and show all the tables/views they belong to in a list
+
+## [1.0.5] - 2018-05-11
+### Fixed
+- Status bar text when connection is not labelled
+
+## [1.0.4] - 2018-05-11
+### Added
+- Display label for postgres connections by @peterbam
+- Rename command for display label
+
+## [1.0.3] - 2018-05-10
+### Added
+- Show "Run Query" command errors using notifications
+
+## [1.0.2] - 2018-05-09
+### Added
+- Support for DB Views in the database explorer and code completion
+
+## [1.0.1] - 2018-05-07
+### Added
+- Support for custom activity bar
+
+## [1.0.0] - 2018-05-05
+### Fixed
+- Connection button, now properly asks for the connection instead of the database.
+
+### Added
+- Syntax highlighting
+- Connection aware code completion (keywords, functions, tables, and fields)
+- In-line error detection powered by EXPLAIN (one error per query in editor)
+- *__Basic__* function signature support (connection aware)
+
+## [0.0.6] - 2018-04-30
+### Fixed
+- Repository link
+- Output Console Name for Language Service
+
+### Added
+- Ability to save results to JSON, XML, or CSV.
+
+## [0.0.5] - 2018-04-30
+- Initial release

package/dist/assets/ckolkman.vscode-postgres-1.4.3.vsix/README.md

@@ -0,0 +1,86 @@
+# PostgreSQL
+
+This is a query tool for PostgreSQL databases.  While there is a database explorer it is _NOT_ meant for creating/dropping databases or tables.  The explorer is a visual aid for helping to craft your queries.
+
+There is a language service that should keep at most a single connection open to the database (assuming one was selected).  This facilitates query diagnostics, code completion, and function signatures.  All code completion keywords, functions, tables, and field names are pulled from the current connection to try to keep everything relevant.
+
+It is possible there are some queries that won't run and report problems - even if they are completely valid (`DROP DATABASE` comes to mind).
+
+> *__Note__: PostgreSQL versions before 9.4 are not supported.*
+
+> *__Note__: AWS RedShift is _also_ not supported - there are information schema queries needed that just won't work there*
+
+## Features
+
+* Management of PostgreSQL connections
+* List Servers/Database/Functions/Tables/Columns (primary key/type)
+* Quickly select top * (with limit) of a table
+* Run Queries
+  * All queries in a pgsql file (; delimited)
+  * Selected query in pgsql file
+  * Selected query in ANY file (via context menu or command palette)
+* Individual editors can have different connections
+* Quickly change connection database by clicking the DB in the status bar
+* Syntax Highlighting
+* Connection aware code completion (keywords, functions, tables, and fields)
+* In-line error detection powered by EXPLAIN (one error per query in editor)
+* *__Basic__* function signature support (connection aware)
+
+## Usage
+
+### Managing Connections
+
+You can add a PostgreSQL connection in the explorer or via the command palette command "PostgreSQL: Add Connection"
+
+![connection](https://github.com/Borvik/vscode-postgres/raw/HEAD/images/add_connection.gif)
+
+You can remove connections from the connection context menu or the command palette command "PostgreSQL: Delete Connection".
+
+![delete_connection](https://github.com/Borvik/vscode-postgres/raw/HEAD/images/delete_connection.gif)
+
+Each item in the explorer has it's own context menu, and you can start a new query from _any_ level (or the command palette "PostgreSQL: New Query").
+
+The "Refresh Items" option reloads the sub-nodes for that item, useful if there were structural changes to the database and you want the explorer to reflect them.
+
+Tables have the extra option to "Select Top 1000" or "Select Top...". They both open a new query with a "SELECT *" query started and run it.  The latter option will prompt you for the quantity first.
+
+### Running Queries
+
+Each editor window can have a different database and/or connection used for its queries.  All windows start with no connection selected.
+
+![status](https://github.com/Borvik/vscode-postgres/raw/HEAD/images/current_connection.png)
+
+Clicking on the server ("localhost" above) or the database name will allow you to quickly change the database.  You can also initiate the change from the command palette.
+
+Windows with their language set to Postgres will get syntax highlighting, and when there is connection selected: code completion, signature information, and diagnostics.
+
+In Postgres language files you can run a query via F5, context menu, or command palette.  You can also run a query from any other file type as long as a connection is selected and you have the query selected - __*F5 will not work for other file types*__.
+
+![run_queries](https://github.com/Borvik/vscode-postgres/raw/HEAD/images/run_queries.gif)
+
+Running queries in Postgres language files first check if anything is selected. If there is a selection, that is run as the query, otherwise all the queries in the editor are run.
+
+Multiple queries are supported. If there is output from more than one query, multiple tables are shown in the results window.
+
+### Serializing Query Results
+
+You can serialize your query results as well.
+
+![save_results](https://github.com/Borvik/vscode-postgres/raw/HEAD/images/save_results.png)
+
+If you have more than one table of results, you will be prompted for the table you wish to serialize.
+
+You can choose from three formats: json, xml, and csv.  The results will be converted to the appropriate format and opened in a new editor of the selected type.
+
+## Extension Settings
+
+This extension contributes the following settings:
+
+* `vscode-postgres.showExplorer`: enable/disable the database explorer.
+* `vscode-postgres.prettyPrintJSONfields`: set to `true` to enable nicely formatted JSON in the query results window.
+* `vscode-postgres.setConnectionFromExplorer`: set to `ifunset` to only set the query connection if not already set.
+* `vscode-postgres.tableColumnSortOrder`: set to `db-order` to sort columns like the database does, `alpha` to sort alphabetically, and `reverse-alpha` for descending alphabetically.
+* `vscode-postgres.intervalFormat`: set to `iso_8601` to format intervals according to the ISO 8601 standard, `humanize` to format as easy to read text, and `succinct` to format like a countdown clock.
+* `vscode-postgres.virtualFolders`: set to array of virtual folders to be displayed under schema. Supported values for virtual folders are `functions`. Set to `null` or empty array `[]` to disable virtual folders.
+* `vscode-postgres.defaultConnection`: set the default connection (by name) that should be used for any file.
+* `vscode-postgres.defaultDatabase`: set the default database on the default connection that should be used for any file (must exist on server).