mirror of
https://github.com/microsoft/vscode.git
synced 2025-12-11 18:41:06 -06:00
fix some spelling mistakes, fix grammar
parent
783e092a2f
commit
44f0caa54e
@ -15,7 +15,7 @@
|
||||
* [issue #15579](https://github.com/Microsoft/vscode/issues/15579): Regex search issue
|
||||
* seed search string only if the selection is created explicitly (i.e. not due to a find match)
|
||||
* Widget size/position
|
||||
* [x] Make it resizeable: [#2657](https://github.com/Microsoft/vscode/issues/2657), [#2220](https://github.com/Microsoft/vscode/issues/2220)
|
||||
* [x] Make it resize-able: [#2657](https://github.com/Microsoft/vscode/issues/2657), [#2220](https://github.com/Microsoft/vscode/issues/2220)
|
||||
* [x] Bug, Replace Box in Current File Truncated [#5861](https://github.com/Microsoft/vscode/issues/5861)
|
||||
* [x] Cover search result: [#5525](https://github.com/Microsoft/vscode/issues/5525)
|
||||
* Multiline search
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
Code consists of a layered and modular `core` that can be extended using extensions. Extensions are run in a separate process refered to as the
|
||||
Code consists of a layered and modular `core` that can be extended using extensions. Extensions are run in a separate process referred to as the
|
||||
`extension host.` Extensions are implemented by utilizing the [extension API](https://code.visualstudio.com/docs/extensions/overview).
|
||||
|
||||
# Layers
|
||||
@ -24,7 +24,7 @@ The `core` of Code is fully implemented in [TypeScript](https://github.com/micro
|
||||
|
||||
# Dependency Injection
|
||||
|
||||
The code is organised around services of which most are defined in the `platform` layer. Services get to its clients via `constructor injection`.
|
||||
The code is organized around services of which most are defined in the `platform` layer. Services get to its clients via `constructor injection`.
|
||||
|
||||
A service definition is two parts: (1) the interface of a service, and (2) a service identifier - the latter is required because TypeScript doesn't use nominal but structural typing. A service identifier is a decoration (as proposed for ES7) and should have the same name as the service interface.
|
||||
|
||||
|
||||
@ -4,7 +4,7 @@ A pre-release of the [December update](../issues/917) is now available on the so
|
||||
|
||||
We love getting feedback on the pre-release and you can help us in many ways:
|
||||
- test new features as described in the [[December Test Plan]].
|
||||
- verify the bugs you have filed and that are targetting the December milestone [bug fixes](https://github.com/Microsoft/vscode/issues?q=is%3Aissue+is%3Aclosed+label%3Abug+milestone%3A%22Dec+2015%22).
|
||||
- verify the bugs you have filed and that are targeting the December milestone [bug fixes](https://github.com/Microsoft/vscode/issues?q=is%3Aissue+is%3Aclosed+label%3Abug+milestone%3A%22Dec+2015%22).
|
||||
|
||||
## Reporting Issues
|
||||
When reporting issues please mention in the comment that you found the issue in the `insiders` release and follow our reporting issues guidelines [[Submitting-Bugs-and-Suggestions]].
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
Extension API Process
|
||||
=
|
||||
|
||||
The goal of this process is to be transparent about how API is created, what phases a proposal goes through, and to know what proposals are finalised when. Still, we want to maintain flexibility in making API.
|
||||
The goal of this process is to be transparent about how API is created, what phases a proposal goes through, and to know what proposals are finalized when. Still, we want to maintain flexibility in making API.
|
||||
|
||||
About Proposed API
|
||||
--
|
||||
|
||||
@ -64,7 +64,7 @@ During the iteration planning process we use the following sources as input:
|
||||
- Review feature requests with many reactions.
|
||||
Issues we plan to work on during an iteration are assigned to the current milestone.
|
||||
|
||||
## Filing bugs as development team member
|
||||
## Filing bugs as a development team member
|
||||
When team members files a bug they perform steps of the inbox tracker for the issue they filed. Therefore bugs filed by the development team do not need to be triaged by the inbox tracker.
|
||||
|
||||
## Verification
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user