Added fine grained permission checks

[AntonioAngelino]

I've added the following permission checks to the filebrowser views:

• can_list_files
• can_view_files
• can_add_files
• can_edit_files
• can_rename_files
• can_delete_files
• can_add_directories

[sehmaschine]

Very nice ... we'll consider this with the next major release. I don't think it's a good idea to implement this with a minor version update.

[sehmaschine]

@AntonioAngelino sorry for the delay, but I have one more question. If we add the permissions, what about existing setups? One needs to assign the permissions to every existing editor, right?

[AntonioAngelino]

Hi @sehmaschine, yes, you're right.
A migration command may be in charge of creating all required permissions.

[sehmaschine]

@AntonioAngelino What about adding a setting like FILEBROWSER_USE_PERMISSIONS which is False by default? This would be backwards compatible. If someone sets it to True, he needs to assign the permissions to editors (which could be documented). Any objections?

[AntonioAngelino]

Even better and KISS-like :)