Closed mousetraps closed 6 years ago
PR incoming. The fix is two-fold:
Actually, nevermind - missed this PR :) https://github.com/VulcanJS/Vulcan/pull/2031
Edit: I'll keep the issue open anyways since it hasn't been merged.
As you pointed out in the issue, #2031 is supposed to solve this issue.
The syntax registerComponent( {name:'MoviesList', component: MoviesList })
is the new syntax since v1.12.0 , which is why I used this syntax when updating the package example-movies. I think it's good to keep it with the new syntax to help enforce it and avoid teaching the old way to the new people.
So just wait until @SachaG merges #2031 ;)
Ahh, I see - thanks! Didn’t realize that was the new syntax. I’ll update the PR to do the opposite, then. I’d assumed the preferred syntax was the one most commonly used in the starter.
Sent from my Rotary Phone
From: Apollinaire Lecocq notifications@github.com Sent: Tuesday, September 11, 2018 2:51 AM To: VulcanJS/Vulcan Cc: Sara Itani; State change Subject: Re: [VulcanJS/Vulcan] http://localhost:3000/components page fails to load when hocs is unspecified (#2061)
As you pointed out in the issue, #2031https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FVulcanJS%2FVulcan%2Fpull%2F2031&data=02%7C01%7C%7C62233c40bfc6445cff0508d617cc23ab%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636722562863933664&sdata=lWU25N0gl5z26KCfYUyAdDtV6ZrviRF%2FjvAGfhZsfcQ%3D&reserved=0 is supposed to solve this issue. The syntax registerComponent( {name:'MoviesList', component: MoviesList }) is the new syntax since v1.12.0 https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmedium.com%2F%40sachagreif%2Fvulcan-js-1-12-a-better-graphql-api-for-crud-operations-fae82e03a7e9%23772f&data=02%7C01%7C%7C62233c40bfc6445cff0508d617cc23ab%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636722562863933664&sdata=r1JpM2e%2B0zgjNnN54pFgLlyXOux9%2FwgpeL51lX264%2Fo%3D&reserved=0 , which is why I used this syntax when updating the package example-movies. I think it's good to keep it with the new syntax to help enforce it and avoid teaching the old way to the new people. So just wait until @SachaGhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSachaG&data=02%7C01%7C%7C62233c40bfc6445cff0508d617cc23ab%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636722562863933664&sdata=43Pva64M3j6nQceJHkRYrmxhtpnHDTxcdHC4zSo34nQ%3D&reserved=0 merges #2031https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FVulcanJS%2FVulcan%2Fpull%2F2031&data=02%7C01%7C%7C62233c40bfc6445cff0508d617cc23ab%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636722562863933664&sdata=lWU25N0gl5z26KCfYUyAdDtV6ZrviRF%2FjvAGfhZsfcQ%3D&reserved=0 ;)
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FVulcanJS%2FVulcan%2Fissues%2F2061%23issuecomment-420215448&data=02%7C01%7C%7C62233c40bfc6445cff0508d617cc23ab%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636722562864089916&sdata=m6BYXrefzpXmHUJGYZ13OZOdS4ejNI7TnXEchW0Ekkw%3D&reserved=0, or mute the threadhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAuj4D8lzUxv8oZoa__YN5xZks9tOGZ0ks5uZ4ecgaJpZM4Wir5Y&data=02%7C01%7C%7C62233c40bfc6445cff0508d617cc23ab%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636722562864089916&sdata=xTSX85ipyu0sT2zdfyCB6JIJVXmvTm%2FQBQPluFEMuNI%3D&reserved=0.
I’d assumed the preferred syntax was the one most commonly used in the starter.
Most of the starters have not been updated yet, since v1.12 has been released only 2 weeks ago, but eventually they will be updated and fixed ;)
Reproduced using the
getting-started
andexample-movies
packages in Vulcan-Starter.Stack trace below. The error occurs when the component is registered as follows (without specifying hocs)
Specifying
hocs: []
or separating out into multiple arguments works.