pushingit
commented
7 years ago The issue seems to be that in the example: import { f7Page, f7Navbar, f7BlockTitle, f7Block } from 'framework7-vue'
Those return nothing, and the page's component export ended up assigning f7Page, etc to null which was being associated with the proper html element names as well.
I took out the importing and component definitions entirely and it started working, all f7-vue components being implicitly read correctly.
I've been having the problem of the stock framework7-vue compnents not getting loaded or found properly, I've tried different versions of framework7/framework7-vue in the 2.x branches, currently with v2.0.0-beta.3 for both, Vue 2.5.2... (In my case this is all going through browserify)
First of all I had the initial problem of the kitchen sink example using "import {Framework7Vue}" where I also had to instead use "import Framework7Vue".... Then in the initial page I use the stock components imported in the page (f7Statusbar etc) don't work as mentioned in the kicken sink - I can't pass the CamelCase versions of the components, apparently their "name" attributes aren't getting read, I have to pass the exported components hash keys from the pages as having their html element (f7-statusbar, f7-panel, etc)... "export default { components: {'f7-statusbar': f7Statusbar}}"
However any of the subsequent f7-vue components that get called from the initial ones aren't being recognized as registered.... For example if the f7Page component uses any other f7-vue component, it complains that that component is not registered... Taking a look at the Vue object it seems like the Vue.options.components hash is filled with MixedCase keys to all of the components but they aren't being found (I think the "name" property isn't being read/found correctly)...