search

w3c / miniapp-manifest

MiniApp Manifest
https://w3c.github.io/miniapp-manifest/
Other
7 stars 8 forks source link

About the `pages` member #35

Closed xfq closed 2 years ago

xfq commented 3 years ago

https://w3c.github.io/miniapp-manifest/#pages-member

pages member During the MiniApp development process, adding or deleting MiniApp pages is done by configuring the list of references. When configuring the page routes, the file name extension MAY be omitted (e.g., /component/mypage).

I have two questions about this.

  1. Why is the example /component/mypage instead of something like pages/index? Per https://w3c.github.io/miniapp-packaging/#sec-pages-directory the directory seems to be named pages.
  2. What should the developer write when the extension is NOT omitted?
espinr commented 2 years ago

Thanks for the heads-up @xfq

  1. I'll change this example to be aligned with the packaging spec. You are right.
  2. The developer may want to indicate the extension of the main document that defines the page or component. So, it should be the .html extension (/pages/index.html or /pages/index).

Any other point of view?