Make a few types exact

Summary: We have some types that could benefit from being exact. In general these are preferable for reasons of control and safety.

Reviewed By: dunnbobcat

Differential Revision: D20637710

fbshipit-source-id: 5d6090c51309eff2154406da2de6ec5948ec9360

src/component/selection/DOMDerivedSelection.js

@@ -13,8 +13,7 @@
 
 import type SelectionState from 'SelectionState';
 
-export type DOMDerivedSelection = {
+export type DOMDerivedSelection = {|
   selectionState: SelectionState,
   needsRecovery: boolean,
-  ...
-};
+|};

src/component/selection/DraftOffsetKeyPath.js

@@ -11,9 +11,8 @@
 
 'use strict';
 
-export type DraftOffsetKeyPath = {
+export type DraftOffsetKeyPath = {|
   blockKey: string,
   decoratorKey: number,
   leafKey: number,
-  ...
-};
+|};

src/component/selection/getDraftEditorSelectionWithNodes.js

@@ -21,11 +21,10 @@ const invariant = require('invariant');
 const isElement = require('isElement');
 const nullthrows = require('nullthrows');
 
-type SelectionPoint = {
+type SelectionPoint = {|
   key: string,
   offset: number,
-  ...
-};
+|};
 
 /**
  * Convert the current selection range to an anchor/focus pair of offset keys

src/component/selection/getRangeBoundingClientRect.js

@@ -13,15 +13,14 @@
 
 const getRangeClientRects = require('getRangeClientRects');
 
-export type FakeClientRect = {
+export type FakeClientRect = {|
   left: number,
   width: number,
   right: number,
   top: number,
   bottom: number,
   height: number,
-  ...
-};
+|};
 
 /**
  * Like range.getBoundingClientRect() but normalizes for browser bugs.