Taha Hassan Mujaddadi

Results 22 comments of Taha Hassan Mujaddadi

This is how our folder structure looks like for one feature and it works quite good for us. ![Folder](https://user-images.githubusercontent.com/2556882/70426276-67067f00-1a7b-11ea-8dad-230777b5816a.png)

I have the same issue. If I refresh the URL, it fires an action but saga doesn't catch that action but when I change something in code and page hot...

yes came here for the same issue https://github.com/request/request/issues/2926

That also doesn't work ``` class CustomTimePickerModal extends React.Component { constructor(props){ super(props); this.state = { value: this.props.defaultValue }; } onChange = value => { this.setState({ value: value }); this.props.onChange(value) }...

That's how I am passing the value to the custom component ` defaultValue={moment(task.realizedStartTime)}`

That's the moment object which is created ![s](https://user-images.githubusercontent.com/2556882/33274340-6d5e7064-d398-11e7-9106-f3b532f1aa70.jpg)

That formated value was passed to placeholder prop not to value `placeholder={`${moment().format('hh:mm')}` || `${moment().format('hh:mm')}`} `

Here is it https://codesandbox.io/s/zqww68629p As you can check it doesn't return the correct value in the console.

I think the issue was probably related to call back as I am getting the correct value in the component call back who is using the date picker.

@Rainpia I started using some other date picker. As you can see this issue is almost 2 years old and still open, I don't have hope that the developer has...