ionic-team / ionic-team/ionic-framework
bug: ion-datetime (and other components) throw `instance[watchMethodName] is not a function` when used inside inline IonModal (React)
- Lingua principale
- TypeScript
- Stelle
- 52.7k
- Fork
- 13.3k
- Merge medio
- 1g 15h
- PR unite (30g)
- 51
Descrizione
### Prerequisites
- [x] I have read the [Contributing Guidelines](https://github.com/ionic-team/ionic-framework/blob/main/docs/CONTRIBUTING.md#creating-an-issue).
- [x] I agree to follow the [Code of Conduct](https://ionicframework.com/code-of-conduct).
- [x] I have searched for [existing issues](https://github.com/ionic-team/ionic-framework/issues) that already report this problem, without success.
### Ionic Framework Version
v7.x
### Current Behavior
```
TypeError: instance[watchMethodName] is not a function
at Datetime.set [as min]
at attributeChangedCallback
```
### Expected Behavior
Ionic components should not throw runtime errors when used inside IonModal, even when controlled via React props.
At minimum:
• setting props like min, value, or isOpen should be safe
• or Ionic should document that this pattern is unsupported
### Steps to Reproduce
```
const Example = () => {
const [open, setOpen] = useState(true);
return (
);
};
```
### Code Reproduction URL
null
### Ionic Info
This affects multiple components that using Overlay
### Additional Information
_No response_
Guida per i contributori
Apri la guida per i contributori
Valutazione
Questa issue non è ancora stata valutata.