Paragraph type permissions conflicts with view unpublished paragraph permission

This might have existed from before we had the logic in paragraphs itself? Does anything break if you just remove it? If yes, what if you return neutral() in that case instead of forbidden?

Ok, that makes sense. It doesn't forbid nor explicitly allow access, letting others make that decision then.

I suppose one question is how it overlaps. E.g., if you have view unpublished but not view type X, should you then be able to see an unpublished paragraph of type X or only when you have both permissions?

tests are really important for access related things, so lets make whatever we decide explicit with test coverage.

\Drupal\paragraphs_type_permissions\Tests\ParagraphsTypePermissionsTest has some existing unpublished tests, making sure that users can't access them anymore. Lets extend that with a use that does have the unpublished permission.

same issue for me - the paragraphs displays incorrectly with inline entity form mode if it's unpublished and current user have permission to view unpublished paragraphs

and here is new patch: the difference mostly in code stylistic + few access check added + notice that it's not good idea to cache the access check results when entity is unpublished

damn, sorry - logic mismatch

Team any solution we can get for this issue ?

Thanks,
Dhruv

Updated #10 patch, where i remove statement that prevent execute permission checks on "view" operation

In case someone else needs this.

Here is a patch that combines the mutually exclusive patches from this issue (#18) and #3056358: Add option to set permission to view/edit/create/delete any paragraph type when using paragraphs type permissions (merge req).

This patch will display unpublished when using paragraphs_type_permissions AND add the CRUD permissions for 'any paragraph'.

The view any paragraph for anonymous avoids the common mistake of creating a paragraph and not granting view permission.