fix: menu list as template - #163

@dword-design Thank you for your contribution! But could you make the PR to dev branch?

@kikuomax done

@dword-design @wesdevpro Please give me some time to see if there might be potential drawbacks.

@dword-design @wesdevpro I will look into this PR after I finish #159.

I turned the menu list into a template, first for consistency and the function implementation didn't work in Nuxt production.

@dword-design Did you mean functional components wouldn't work in Nuxt production in general?

I turned the menu list into a template, first for consistency and the function implementation didn't work in Nuxt production.

@dword-design Did you mean functional components wouldn't work in Nuxt production in general?

@kikuomax Ok I debugged myself into this and I think the problem is that we use component.name to register the components in the plugins. This is generally not a problem since also for functional components component.name will be the name of the function (in this case BMenuList). But in production and in the browser the function name will be a generated one (in this case ng), so the component name is wrong. In other cases we explicitly set the name as a fiel via Options API. So functional components aren't directly a problem in Nuxt but it's more how it's solved in Buefy.

@dword-design Great insight!

Now, I remember I faced the exact problem fixed at d44e6d2 that is not merged to main branch yet.

@dword-design Great insight!

Now, I remember I faced the exact problem fixed at d44e6d2 that is not merged to main branch yet.

While the problem should have already been solved, I think an ordinary component is more intuitive and this PR is still relevant.