refactor: change codebase into material-ui #2
Conversation
|
|
||
| import { useFormFields } from '../libs/hooksLib'; | ||
|
|
||
| function StripeInput(props) { |
There was a problem hiding this comment.
Hey @xuatz
I was trying to integrate the react-stripe-elements into material-ui unfortunately they don't have a clean way of doing it. One of the author of material-ui created a snippet. TextField component of material ui have a InputProps property which in a way you could override the default component by passing a custom props. It's not actually documented on their web unfortunately.
But they have a topic for it here:
mui/material-ui#16037
| const [isLoading, setIsLoading] = useState(true); | ||
|
|
||
| useEffect(() => { | ||
| async function onLoad() { |
There was a problem hiding this comment.
why do you need to create new onLoad() every time?
There was a problem hiding this comment.
Hey @xuatz
Sorry, I didn't change the logic of the application boilerplate currently. So there are questionable logic in the current state of the app. They will be moved out after I integrated redux/redux-saga
|
|
||
| function loadNotes() { | ||
| return API.get('notes', '/notes'); | ||
| } |
xuatz
changed the title
Hi everyone!
I did not change any logic on the app. The app works as it is, this branch purpose was to make sure to remove the react-bootstrap dependencies/components and move to material ui one. Also I didn't remove the packages yet for
react-bootstrap.The design is kind of meh as of now, since my main focus was to make it work for material ui.
Problem faced:
There's this warning using the stripe elements with material ui, can't seem to rid of it.
Material UI have this "hackish" way of using stripe elements.
Problem can be seen at this commit: 4d4bebf
See this post/issue from material ui:
mui/material-ui#16037