Update my name in most places
Sophie Alpert committed
Sep 8, 2017 at 15:43 UTC
2aa4988379144c5c05ef57b876cd4aedd1b1d61a
14 files changed
+20
-18
docs/_data/authors.yml
+3
-3
@@ -58,9 +58,9 @@ schrockn:
58
sebmarkbage:
59
name: Sebastian Markbåge
60
url: https://twitter.com/sebmarkbage
61
-spicyj:
62
- name: Ben Alpert
63
- url: http://benalpert.com
61
+sophiebits:
62
+ name: Sophie Alpert
63
+ url: https://sophiealpert.com
64
steveluscher:
65
name: Steven Luscher
66
url: https://twitter.com/steveluscher
docs/_posts/2014-02-16-react-v0.9-rc1.md
+1
-1
@@ -1,6 +1,6 @@
1
---
2
title: React v0.9 RC
3
-author: spicyj
3
+author: sophiebits
4
---
5
6
We're almost ready to release React v0.9! We're posting a release candidate so that you can test your apps on it; we'd much prefer to find show-stopping bugs now rather than after we release.
docs/_posts/2014-02-20-react-v0.9.md
+1
-1
@@ -1,6 +1,6 @@
1
---
2
title: React v0.9
3
-author: spicyj
3
+author: sophiebits
4
---
5
6
I'm excited to announce that today we're releasing React v0.9, which incorporates many bug fixes and several new features since the last release. This release contains almost four months of work, including over 800 commits from over 70 committers!
docs/_posts/2015-03-10-react-v0.13.md
+1
-1
@@ -1,6 +1,6 @@
1
---
2
title: "React v0.13"
3
-author: spicyj
3
+author: sophiebits
4
---
5
6
Today, we're happy to release React v0.13!
docs/_posts/2015-03-26-introducing-react-native.md
+1
-1
@@ -1,6 +1,6 @@
1
---
2
title: "Introducing React Native"
3
-author: spicyj
3
+author: sophiebits
4
---
5
6
In January at React.js Conf, we announced React Native, a new framework for building native apps using React. We're happy to announce that we're open-sourcing React Native and you can start building your apps with it today.
docs/_posts/2015-07-03-react-v0.14-beta-1.md
+1
-1
@@ -1,6 +1,6 @@
1
---
2
title: React v0.14 Beta 1
3
-author: spicyj
3
+author: sophiebits
4
---
5
6
This week, many people in the React community are at [ReactEurope](https://www.react-europe.org/) in the beautiful (and very warm) city of Paris, the second React conference that's been held to date. At our last conference, we released the first beta of React 0.13, and we figured we'd do the same today with our first beta of React 0.14, giving you something to play with if you're not at the conference or you're looking for something to do on the way home.
docs/_posts/2015-09-02-new-react-developer-tools.md
+1
-1
@@ -1,7 +1,7 @@
1
---
2
title: "New React Developer Tools"
3
layout: post
4
-author: spicyj
4
+author: sophiebits
5
---
6
7
A month ago, we [posted a beta](/react/blog/2015/08/03/new-react-devtools-beta.html) of the new React developer tools. Today, we're releasing the first stable version of the new devtools. We're calling it version 0.14, but it's a full rewrite so we think of it more like a 2.0 release.
docs/_posts/2015-09-10-react-v0.14-rc1.md
+1
-1
@@ -1,6 +1,6 @@
1
---
2
title: "React v0.14 Release Candidate"
3
-author: spicyj
3
+author: sophiebits
4
---
5
6
We’re happy to announce our first release candidate for React 0.14! We gave you a [sneak peek in July](/react/blog/2015/07/03/react-v0.14-beta-1.html) at the upcoming changes but we’ve now stabilized the release more and we’d love for you to try it out before we release the final version.
docs/_posts/2015-10-07-react-v0.14.md
+1
-1
@@ -1,6 +1,6 @@
1
---
2
title: "React v0.14"
3
-author: spicyj
3
+author: sophiebits
4
---
5
6
We’re happy to announce the release of React 0.14 today! This release has a few major changes, primarily designed to simplify the code you write every day and to better support environments like React Native.
docs/_posts/2015-12-29-react-v0.14.4.md
+1
-1
@@ -1,6 +1,6 @@
1
---
2
title: "React v0.14.4"
3
-author: spicyj
3
+author: sophiebits
4
---
5
6
Happy December! We have a minor point release today. It has just a few small bug fixes.
docs/_posts/2016-01-12-discontinuing-ie8-support.md
+1
-1
@@ -1,6 +1,6 @@
1
---
2
title: "Discontinuing IE 8 Support in React DOM"
3
-author: spicyj
3
+author: sophiebits
4
---
5
6
Since its 2013 release, React has supported all popular browsers, including Internet Explorer 8 and above. We handle normalizing many quirks present in old browser versions, including event system differences, so that your app code doesn't have to worry about most browser bugs.
src/renderers/dom/fiber/wrappers/ReactDOMFiberTextarea.js
+3
-2
@@ -55,8 +55,9 @@ var ReactDOMTextarea = {
55
// Always set children to the same thing. In IE9, the selection range will
56
// get reset if `textContent` is mutated. We could add a check in setTextContent
57
// to only set the value if/when the value differs from the node value (which would
58
- // completely solve this IE9 bug), but Sebastian+Ben seemed to like this solution.
59
- // The value can be a boolean or object so that's why it's forced to be a string.
58
+ // completely solve this IE9 bug), but Sebastian+Sophie seemed to like this
59
+ // solution. The value can be a boolean or object so that's why it's forced
60
+ // to be a string.
61
var hostProps = Object.assign({}, props, {
62
value: undefined,
63
defaultValue: undefined,
src/renderers/dom/stack/client/DOMLazyTree.js
+1
-1
@@ -26,7 +26,7 @@ var setTextContent = require('setTextContent');
26
* In other browsers, doing so is slower or neutral compared to the other order
27
* (in Firefox, twice as slow) so we only do this inversion in IE.
28
*
29
- * See https://github.com/spicyj/innerhtml-vs-createelement-vs-clonenode.
29
+ * See https://github.com/sophiebits/innerhtml-vs-createelement-vs-clonenode.
30
*/
31
var enableLazy =
32
(typeof document !== 'undefined' &&
src/renderers/dom/stack/client/wrappers/ReactDOMTextarea.js
+3
-2
@@ -50,8 +50,9 @@ var ReactDOMTextarea = {
50
// Always set children to the same thing. In IE9, the selection range will
51
// get reset if `textContent` is mutated. We could add a check in setTextContent
52
// to only set the value if/when the value differs from the node value (which would
53
- // completely solve this IE9 bug), but Sebastian+Ben seemed to like this solution.
54
- // The value can be a boolean or object so that's why it's forced to be a string.
53
+ // completely solve this IE9 bug), but Sebastian+Sophie seemed to like this
54
+ // solution. The value can be a boolean or object so that's why it's forced
55
+ // to be a string.
56
var hostProps = Object.assign({}, props, {
57
value: undefined,
58
defaultValue: undefined,