* Support position property in editor component
- This needs to be set directly on the editor component so cannot just use CSSStyles feature
- Given its importance to this scenario, it also warrants a dedicated property.
* Fix window resize when action bar clicked
* Renamed per Abbie's suggestion
* Changed name to clarify the comments
- Fixes#1764, fixes#1765
- Fixes bug where configModifiers were passed in the dashboard service in some places, and a different object with incompatible / missing fields in a different one. Now it always passes in the owner object, and this should have the required fields
- Note: this doesn't fix the problem where the code does not fail to build, which I would have expected to be the case.
- Adds "provider" as an option for TabConfig including in the schema
- Filter by "provider" type when loading tabs. If provider is not set for a tab, will assume "MSSQL" since it's the default provider. This is a design decision - without this, we would either have to disable tabs that don't show this or have them incorrectly show for non-MSSQL provider types
Notes:
Does not override behavior for individual widgets, which still get the current provider set as their provider if not specified. This seems to be required so should be fine.
We will fix tasks/widgets that aren't supported by a provider showing up in a separate PR, since it's a different issue
* change to generic injection
* formatting
* fixed missed merge
* change to keep a record of the services per selector
* formatting
* adding back in tests
* apply back tests
* remove fundamentally broken test
This is an initial PR for a new model-driven UI where extensions can provide definitions of the components & how they're laid out using Containers.
#1140, #1141, #1142, #1143 and #1144 are all tracking additional work needed to improve the initial implementation and fix some issues with the implementation.
Features:
- Supports defining a FlexContainer that maps to a flexbox-based layout.
- Supports creating a card component, which is a key-value pair based control that will lay out simple information to a user. Eventually this will have an optional set of actions associated with it.
- Has a sample project which shows how to use the API and was used for verification
* Initial VS Code 1.21 file copy with patches
* A few more merges
* Post npm install
* Fix batch of build breaks
* Fix more build breaks
* Fix more build errors
* Fix more build breaks
* Runtime fixes 1
* Get connection dialog working with some todos
* Fix a few packaging issues
* Copy several node_modules to package build to fix loader issues
* Fix breaks from master
* A few more fixes
* Make tests pass
* First pass of license header updates
* Second pass of license header updates
* Fix restore dialog issues
* Remove add additional themes menu items
* fix select box issues where the list doesn't show up
* formatting
* Fix editor dispose issue
* Copy over node modules to correct location on all platforms
* commting .d.ts changes
* added serverinfo to .d.ts
* maybe its working?
* works
* updated contrib
* remove unnecessary code
* fix compile errors
* update task schema and add the ability to specifiy a when clause
* update defaults for tasks widget
* add when to restore and back up tasks to not show up for cloud servers
* formatting
* fixing engine
* add restore to server page
