bookmarking a more careful consideration of where to put the /utility folder that would have:
[ non state | non API functionality ]
im testing a return all data from pokeAPI function. I believe such a function could/would belong in the /utility folder.
I want to test that function with graphQL so I'm executing the return all data function from within the server/index.js file
the /utility folder will be in the scope of the react project which would be in the /client folder instead of the /server
For now the test of running the execution from the front end, and the back end dealing with graphQL and return data
if the utility folder is out of the scope of './src' then use of "import from" will be lost if not mistaken
bookmarking a more careful consideration of where to put the /utility folder that would have: [ non state | non API functionality ]
im testing a return all data from pokeAPI function. I believe such a function could/would belong in the /utility folder. I want to test that function with graphQL so I'm executing the return all data function from within the server/index.js file
the /utility folder will be in the scope of the react project which would be in the /client folder instead of the /server For now the test of running the execution from the front end, and the back end dealing with graphQL and return data
if the utility folder is out of the scope of './src' then use of "import from" will be lost if not mistaken
[10:49am]