Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

G3 v2 0 #24

Open
wants to merge 3,308 commits into
base: master
Choose a base branch
from
Open

G3 v2 0 #24

wants to merge 3,308 commits into from

Conversation

usernamealreadyis
Copy link

commit : 406db41

@usernamealreadyis usernamealreadyis added this to the param:new milestone Jan 5, 2016
@usernamealreadyis usernamealreadyis modified the milestones: _delete, param:new Feb 14, 2016
@GistIcon GistIcon locked and limited conversation to collaborators Feb 14, 2016
@alexeagle alexeagle deleted the g3_v2_0 branch September 20, 2016 00:17
@alexeagle alexeagle restored the g3_v2_0 branch September 20, 2016 00:21
@matsko matsko force-pushed the g3_v2_0 branch 3 times, most recently from f14d549 to d4d3782 Compare January 10, 2017 01:14
@mhevery mhevery force-pushed the g3_v2_0 branch 2 times, most recently from 339612a to b4214d6 Compare February 1, 2017 20:42
@mhevery mhevery force-pushed the g3_v2_0 branch 2 times, most recently from 1ece736 to 44bb337 Compare February 11, 2017 18:02
matsko and others added 29 commits March 21, 2017 14:26
…15357)

Unlike in the browser, on the server there is no concept of a document origin.
Thus, it is illegal to make requests for relative URLs against Http on platform-server.

Currently this fails with a vague error:

Error: Uncaught (in promise): Error at resolvePromise

This change adds explicit validation and a friendlier error message:

Error: URLs requested via Http on the server must be absolute. URL: /testing

Another option considered was to track the concept of an origin for the platform
and automatically prepend it to relative URLs. This would cause automatic "local
RPCs" to be made, though, which would be an unexpected and undesirable default
behavior.

Fixes #15349

PR Close #15357
Hopefully this will reduce aio test flakes
This new version fixes the problem with mistaking
content inside inline HTML blocks as tags

Related to #15199
The change from `modules` to `packages` needed to be applied to these links.
The original Rho is too strict when it comes to markdown headings.
It requires that there be a blank line separating the heading and the
next paragraph.  The forked version here fixes that; but the Rho project
will not merge it as it goes against there basic rules.
The navigation.json is now passed through the dgeni pipeline.
The source file has been moved to `aio/content/navigation.json`
but the generated file will now appear where the original source file
was found, `aio/src/content/navigation.json`.

Everything inside `aio/src/content` is now generated and ignored by git.

The `processNavigationMap` processor in this commit adds the current version
information to the navigation.json file and verifies the relative urls in
the file map to real documents.

The navigationService exposes the versionInfo as an observable, which the
AppComponent renders at the top of the sidenav.
This will be replaced by a single file migrated from angular.io
This lowers the `yarn docs` processing time by about 40% (from 50 secs
to 30 secs).
This component sends a lot of messages to the console, which makes the
test run less easy to follow.
The navigation.json is now passed through the dgeni pipeline.
The source file has been moved to `aio/content/navigation.json`
but the generated file will now appear where the original source file
was found, `aio/src/content/navigation.json`.

Everything inside `aio/src/content` is now generated and ignored by git.

The `processNavigationMap` processor in this commit adds the current version
information to the navigation.json file and verifies the relative urls in
the file map to real documents.

The navigationService exposes the versionInfo as an observable, which the
AppComponent renders at the top of the sidenav.
Content pages like `tutorial/index.md` were being mapped to `tutorial.index.json`,
which meant that they could only be rendered if you browsed to `/tutorial/index`.

This didn't sit well so now these pages are mapped to `tutorial.json`, which
means that you browser to them via `/tutorial/` or just `/tutorial`.

Fixed #15335
…est cli blueprint

This shouldn't change anything. But it's interesting that we used to have this  import
that seemed bogus, but there were no compilation or rutime errors.
This commit fixes a regression where `ngModel` no longer syncs
letter by letter on Android devices, and instead syncs at the
end of every word. This broke when we introduced buffering of
IME events so IMEs like Pinyin keyboards or Katakana keyboards
wouldn't display composition strings. Unfortunately, iOS devices
and Android devices have opposite event behavior. Whereas iOS
devices fire composition events for IME keyboards only, Android
fires composition events for Latin-language keyboards. For
this reason, languages like English don't work as expected on
Android if we always buffer. So to support both platforms,
composition string buffering will only be turned on by default
for non-Android devices.

However, we have also added a `COMPOSITION_BUFFER_MODE` token
to make this configurable by the application. In some cases, apps
might might still want to receive intermediate values. For example,
some inputs begin searching based on Latin letters before a
character selection is made.

As a provider, this is fairly flexible. If you want to turn
composition buffering off, simply provide the token at the top
level:

```ts
providers: [
   {provide: COMPOSITION_BUFFER_MODE, useValue: false}
]
```

Or, if you want to change the mode  based on locale or platform,
you can use a factory:

```ts
import {shouldUseBuffering} from 'my/lib';

....
providers: [
   {provide: COMPOSITION_BUFFER_MODE, useFactory: shouldUseBuffering}
]
```

Closes #15079.

PR Close #15256
@IgorMinar IgorMinar deleted the g3_v2_0 branch March 22, 2017 04:53
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.