Difference between visible/hidden

[titantwentyone]

Package

Actions

Package Version

v4.8.2

How can we help you?

Just wanted some clarification. I assumed that when using hidden and visible with actions or fields, that these methods were essentially the opposite of each other and used to ease readability. What I've noticed is that, when testing, these two methods give different results. Just wanted to check that my understanding is correct.

Given I have an action defined as:

Action::make('something')
   ->visible(false)
   
   ...
   ->assertActionExists(TestAction::make('something')) // fails
   ...

This test fails as I understand that the field is never registered and so does not technically exist.

However

Action::make('something')
   ->hidden(true)
   
   ...
   ->assertActionExists(TestAction::make('something')) //succeeds
   ...

This action is regsitered but hidden from the end user.

I have used actions here as I came across this when rewriting some tests but I assume its the same behaviour for fields.

Couldn't see this explicitly in the docs. Insight appreciated!

[webard]

I think assertActionExists should return true in both cases, because technically the action exists, so this seems like a bug. assertActionExists makes sense when actions are added or removed dynamically. Even when using authorize, you should check hidden/visible, not exists.