@IonicPage decorator requires a module per page?


#1

0
down vote
favorite
I have a lot of pages, organizad in folders, I want to have only one module file per each folder and not per each page, its that possible? what should I put in imports? can I use deep linking?

@NgModule({
  declarations: [
    ActivityDetailsPage,
    HobbySelectionPage,
    ConversationModalPage,
    ParticipantsModalPage,
    AddGuestsPage
  ],
  imports: [],
  exports: [
    ActivityDetailsPage,
    HobbySelectionPage,
    ConversationModalPage,
    ParticipantsModalPage,
    AddGuestsPage
  ],
})
export class SharedModule {}

#2

In that case, lazy loading is your friend. So creating individual modules makes a lot of sense.


#3

I tried lazy loading like a month ago and was impossible yo make work that time. Right now I cant tried again, I have to go out with a version of my app. I need to things, 1. Use deeplinking 2. Organize pages, a have a folder structure, and I want to have a module per folder of pages, thats possible? or I have to make a module per each page?


#4

Then the topic of this question is sort of weird, because the @IonicPage decorator is lazy loading.


#5

But only if I call nav.push with name of the page, but I still using the reference to the page class. But what about my question? I need a module per page and import it all on app.module.ts?


#6

Your question doesn’t make any sense, because you’re asking about a lazy loading feature while saying you don’t want lazy loading. If you don’t want lazy loading, there should be no occurrences of @IonicPage in your app at all.


#7

Is not that I don’t want, Is that when I try it it doesn’t works. But I need deep linking.