Error: unrecognized prop `checkOptions`

[barrychapman]

I am getting the following error:

index.js:1 Warning: React does not recognize the `checkOptions` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `checkoptions` instead. If you accidentally passed it from a parent component, remove it from the DOM element. in button (created by e) in e (created by e) in div (created by s) in s (created by e) in e (created by e) in e (created by e) in div (created by c) in c (created by e) in div (created by e) in e (created by e) in div (created by e) in e (at Description.js:25) in Description (at FormElements.js:61) in div (at FormElements.js:60) in TextAreaInput (at RegionAddForm.js:112) in div (created by Row) in Row (at RegionAddForm.js:111) in form (created by Form) in Form (at RegionAddForm.js:72) in Formik (at RegionAddForm.js:55) in RegionAddForm (at RegionAdd.js:114) in div (created by CardBody) in CardBody (at RegionAdd.js:131) in div (created by Card) in Card (at RegionAdd.js:126) in div (created by Col) in Col (at RegionAdd.js:125) in div (created by Row) in Row (at RegionAdd.js:124) in div (at RegionAdd.js:123) in RegionAdd (created by Context.Consumer) in Route (at Admin.js:69) in Switch (at Admin.js:105) in div (at Admin.js:103) in div (at Admin.js:96)

From what I can see, the issue is stemming from the LINK BUTTON in the toolbar.

[TallOrderDev]

We are getting the same issue with the bellow code.

import React, { Component } from "react";
import RichTextEditor from "react-rte";

class EventDescription extends Component {
  state = { value: RichTextEditor.createEmptyValue() };
  onChange = (value) => this.setState({ value });
  render() {
    return <RichTextEditor value={this.state.value} onChange={this.onChange} />;
  }
}
export default EventDescription;

We are seeing checkOptions as a change in the lastest PR. Commit linked below.
dc163e3

Current error with this code pictured.

[machineghost]

I'm not sure what's holding up the release of this (it was literally a one-line change), but in the meantime if anyone wants to get rid of that giant wall of red text in their console, you can use this temporary fix:

"react-rte": "https://github.com/machineghost/react-rte/",

Make sure you npm i after the change. However, I should note that my repo won't get future updates, so this is only a temporary workaround until the fix is released properly.

[akshayDatacode]

Warning: React does not recognize the checkOptions prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase checkoptions instead. If you accidentally passed it from a parent component, remove it from the DOM element.

I am also getting the same error

[JerryLeeCS]

I am getting the same error too.

[maxmoeschinger]

When will you release the fix?

[umarjavedse]

This issue is still not fixed. Please mention how can I solve this issue.

[wasimakram-doodle]

anyone fixed this issue?

[mohammad-mustafa-tfs]

import RichTextEditor from 'react-rte'; // using version: "react-rte": "^0.16.3",

Error: Warning: React does not recognize the checkOptions prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase checkoptions instead. If you accidentally passed it from a parent component, remove it from the DOM element.

its very annoying in clean source development, is there some update or fix for this as on date?

[gcjunior]

I am having the same error:"react-rte": "^0.16.3",
react-dom.development.js:522 Warning: React does not recognize the checkOptions prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase checkoptions instead. If you accidentally passed it from a parent component, remove it from the DOM element.
How can I fix it?

[joefhall]

I'm also getting the same error message. This component works great otherwise -- is a fix possible? Many thanks

[machineghost]

Guys, this smells like a dead library: the last ticket was closed Nov 5, 2020. If you all want to wait for a fix, you can ... but you'll likely be waiting forever because the maintainer seems long gone.

OR, you can switch one line in package.json (see my comment above) and have the issue fixed forever. All you'll lose is future updates to this (again, dead-smelling) library :)

P.S. Of course it would be much better if the maintainer took my code, and then you wouldn't have to rely on a stranger's repo ... but since they don't seem to want to, the matter is out of our control.

However, if you don't want to trust my repo, you can always fork the package yourself, and then make the (super simple) change that I made here: machineghost@3d005c2.

[bahar198]

Just Install " npm i react-rte-17 " package
the Bug Fixed there