jjk
jjk
Note that this component had a decorator with a context and stores.
@qimingweng sorry not immediately I will try and have a look tomorrow - but it may not be easy to resolve.
@qimingweng Yep that would do it.
Actually that might be a red-herring.. But there is probably a style being set or something else causing it to fail, only way to find out is to renderToString and...
@ezequiel Hey, I rebuilt an iso app and modified typeahead - L78 to uniqueId = 'someHardCodedId'; and it no longer throws the error. Let me know when you roll out...
@ezequiel A bit of another issue If you are planning to fix this I wondered if you mind adding on L182 name: props.inputName for those who are using your component...
@ezequiel Yep that's the idea - the reason I ask is if you wrap the item in a form you can use the input even when JS is disabled.. and...
@ezequiel I have tested your update which unfortunately presents a checksum mismatch issue again. However this time I have tried to set a static ID again - and it still...
@ezequiel Same error as before, this is a red hearing though the fault will be somewhere else - when I updated the unique ID before this error was mitigated, however...
@ezequiel any luck? Can I help?