Include file questions

Wappler General
1

I have a couple of general questions about include files.

Wappler only allows the selected section in the App Structure to be transferred to an include file. Is there a technical reason why this is the best approach or is it like this to make it easier to create includes visually, just by using the App Structure panel?

I would find it slightly more convenient if include files were created from the currently selected code rather than the currently-selected selection in App Structure - to make it possible to select more than one section to export to the new file. As it is, I select a single section and then manually add the additional code I want to include. It’s not much of a problem. I just wonder if others have the same issue or if I should approach things differently.

Another matter relating to includes I’m not clear about is the comment section which is prefixed to the exported code (ie the include file). Should this code be updated to reflect changes to the files and components and files it references - either during the current development or in the future? Eg if a different version of jQuery or Fontawesome is used, should any linked include files be updated?

2

I generally just wrap any complex includes in a section tag and include the section as an include. It will include everything in the section.

The comment code is required to be able to work on the include file visually.

3

Thanks Brad. Using sections is a good solution.

I realise the comment code is needed to make the includes easer to work with. I suppose it can be updated manually if necessary - if it would make working with the include easier. Otherwise, I suppose it’s probably not that important. Ideally it would automatically be updated if the original source file is updated, but it’s not much of an issue.