"All crop params are initially optional." When infact they are not

Stated in README and in https://github.com/DominicTobias/react-image-crop/blob/7c4ddb90a7cf33db2b55a7449f5091f769254d50/src/ReactCrop.tsx#L200-L201 but only the aspect-prop is optional: https://github.com/DominicTobias/react-image-crop/blob/7c4ddb90a7cf33db2b55a7449f5091f769254d50/src/ReactCrop.tsx#L164-L171

[nzayatz14]

@DominicTobias making the prop crop a Partial <Crop> object as a parameter fixes the issue of having to pass a full Crop into the component, but it does not fix the issue of declaring a local value as a Crop.

For example, your current definition of a Crop is

export interface Crop {
  aspect?: number;
  x: number;
  y: number;
  width: number;
  height: number;
  unit: 'px' | '%';
}

so, if I wanted to create a local state variable to store the current crop in my component, it may look something like

const [myCrop, setMyCrop] = useState<Crop>({ unit: '%', width: 50, aspect: 1 }); //this throws a type error

This particular line, however, would throw a TypeError because my initial state value of { unit: '%', width: 50, aspect: 1 } is missing the parameters height, x, and y.

I believe removing the Partial<> from the propType and changing the type definition of Crop to be:

export interface Crop {
  aspect?: number;
  x?: number;
  y?: number;
  width?: number;
  height?: number;
  unit?: 'px' | '%';
}

may just work, though I do not know if you need any of those fields to be required specifically.

Hope this sheds some light on the issue.

[DominicTobias]

This has changed in v10 (along with many breaking changes) and is no longer an issue as a complete crop always has to be passed in. Check the release notes for more info.