No More Posting New Topics!

If you have a question or an issue, please start a thread in our Github Discussions Forum.
This forum is closed for new threads/ topics.

Navigation

    Quasar Framework

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    Naming Convention change?

    Framework
    2
    3
    666
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      steve last edited by

      I noticed around version v0.17.0 the naming conventions changed for the StarterKit in which pages and layout files are now Capitalized and routes now include full file name and extention.

      import('layouts/Layout.vue'),
      

      It there a reason for this, benefit or just following some other guidelines?
      Are there other naming convention that have been changed elsewhere?

      I have existing projects and new projects and want to make sure I update accordingly. Thx!

      1 Reply Last reply Reply Quote 0
      • G
        genyded last edited by

        Well, it’s “common practice” today to name any single file Vue components starting with a capital letter (it used to be the opposite). The Layout and Page that Quasar installs with are intended to serve as examples. There is no hard and fast rule though. You can name them however you like. It’s best to be consistent whatever you decide though.

        1 Reply Last reply Reply Quote 0
        • S
          steve last edited by

          It looks like they are following the prescribed style guide from Vue.js, naturally.
          https://vuejs.org/v2/style-guide/#Component-files-strongly-recommended

          1 Reply Last reply Reply Quote 0
          • First post
            Last post