CyberMages/mason
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

Handle resource for Plugins/Templates/Add-ons #1

New Issue
Open
opened 2016-08-03 19:12:41 -04:00 by myrddin · 1 comment
myrddin commented 2016-08-03 19:12:41 -04:00 (Migrated from gitlab.com)
Copy Link

Right now resources.msnr is a single file that has to be updated for any resource addition. What happens though when a new plugin/template/add-on is added? Right now the resources.msnr needs to be manually updated to add the resources of the plugin/template/add-on. This is tedious, and unmanageable as projects get bigger and change what plugins/templates/add-ons are installed.

To fix it is suggested to add a step to the build process that will recursively look through the resources directory to find resources.msnr files. It will then use the current location of the msnr file as the working directory when processing that file. All files processed in this way will then be joined as a single msnl when set to the output directory. To stay consistent, and easy for the code behind files, resource names will still have to managed by the user and non unique names should be called out during build and throw an error.

Right now resources.msnr is a single file that has to be updated for any resource addition. What happens though when a new plugin/template/add-on is added? Right now the resources.msnr needs to be manually updated to add the resources of the plugin/template/add-on. This is tedious, and unmanageable as projects get bigger and change what plugins/templates/add-ons are installed. To fix it is suggested to add a step to the build process that will recursively look through the resources directory to find resources.msnr files. It will then use the current location of the msnr file as the working directory when processing that file. All files processed in this way will then be joined as a single msnl when set to the output directory. To stay consistent, and easy for the code behind files, resource names will still have to managed by the user and non unique names should be called out during build and throw an error.
myrddin commented 2019-07-17 23:14:46 -04:00 (Migrated from gitlab.com)
Copy Link

unassigned @myrddin

unassigned @myrddin
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
myrddin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: CyberMages/mason#1
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?