You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would help general readability if the import statement read
import { makeFunctionCallSchema } from '@utils/validation/makeFunctionCallModal';
Coming up with aliases for common paths accessed throughout the app will help us reason through code better and avoid 'import hell' while also forcing us to reason through the most proper places to put our code.
What do you think about having aliases for the following folders inside of src/ -> @store/, @ui/, @near/, @config/, @utils/.
One caveat is that we will need to use Craco(preferred) or react-app-rewired instead of react-scripts because react-scripts does not allow for custom webpack configurations.
I personally don't like how the folder schema is done now - I feel like it's counterintuitive, but this is how we inherited it. I would prefer to clean it up at some point vs introducing aliases. What do you think @Patrick1904@judith-Near@hcho112 ?
It would help general readability if the import statement read
import { makeFunctionCallSchema } from '@utils/validation/makeFunctionCallModal';
Coming up with aliases for common paths accessed throughout the app will help us reason through code better and avoid 'import hell' while also forcing us to reason through the most proper places to put our code.
What do you think about having aliases for the following folders inside of
src/
->@store/
,@ui/
,@near/
,@config/
,@utils/
.One caveat is that we will need to use Craco(preferred) or react-app-rewired instead of
react-scripts
because react-scripts does not allow for custom webpack configurations.Originally posted by @roshaans in #134 (comment)
The text was updated successfully, but these errors were encountered: