fields display as required when not required

I tried changing one of the fields to use the Core required strategy and to not be required; the red asterisk went away. I then changed it back to required by state, and the asterisk came back. I also tried changing it to required by role with a role the current user does not have, and again the field showed as required when it should not be. So this is not a problem with the submodules, it's with the API module.

I tried uninstalling the required_api module altogether and then re-enabling just required_by_content_moderation_state and required_api, with the same result - the field is displayed as required when it should not be. I then uninstalled again and re-enabled just required_by_role and required_api, and had the same result. So I'm starting to think version 3 of this module just doesn't work at all. I'll stick with version 2 for now.

Yeah, there's an open issue: 🐛 Major error on content with required by role Active . I was waiting for the person who reported it to review the fix, but it looks like that's not happening, so I'll just merge and release it.

I created required_by_role 2.0.0-beta3 → , could you try to update and see if that fixes your issue? Thanks.

@dieterholvoet thank you for pointing that out! I'll see if I can adapt that 2.0 fix for 3.0. Let's leave this ticket open until we have a 3.0 fix.

No, 2.0.0-beta3 is the latest version of required_by_role and 3.0.0-beta1 is the latest version of required_api. Both can be used together.

@benstallings could you confirm if the latest versions of both modules fixed the issue you're having?

@dieterholvoet I wound up just writing custom code to solve my immediate need rather than using this module, so I don't know, sorry!