Ellpeck
Deleting content that is not in content folder?
If someone renames a file this breaks. Try to check if the file still exists that is referenced in the mgcb, if it doesn't remove it before trying to add it back again
Hi! Contentless doesn't remove content items from the content builder file if they were moved or don't exist anymore, and it's not meant to do so either. Contentless only adds new content files to the content builder based on its default rules or the rules laid out in your Contentless.json config file. If you remove a file, you have to remove it manually from the content builder file as you would if you weren't using Contentless. I hope that answers your question, but let me know if it hasn't!
@Ellpeck Why is the content not synced with the stuff in the folder though? It's suppose to be contentless not require us to open the mgcb every time a reference breaks. If someone renames or deletes a asset it should update it accordingly in the content. At least make it an option.
As advertised, Contentless is a tool for adding assets to the content pipeline, not updating or changing existing ones. A key part of the philosophy of Contentless is the following, as described in the README:
As Contentless never changes any existing content of a Content.mgcb file, all changes that are made to it by hand or using the Content Pipeline tool will not be overridden.
Sorry if this is not a policy you agree with!
Hi! I've gone back and forth on this and decided that, especially with #3 as a new suggestion, it might be nice to have this as a feature that is disabled by default, but can be enabled in the Contentless.json file per project!