Use select fields where it makes sense #4
Conversation
joshuapease
force-pushed
the
jp/use-select-fields
branch
from
a544801
to
2fa37ab
Compare
| self::PROPERTY_PLUGINS => [ | ||
| 'class' => MultiSelectDb::class, | ||
| ], | ||
| self::PROPERTY_PLUGIN_VERSIONS => [ | ||
| 'class' => MultiSelectDb::class, | ||
| ], |
There was a problem hiding this comment.
There's a plugin & plugin versions column.
The plugin column will let you filter by what plugins are installed by site.
But if you ever need to check for specific versions, you can also choose that.
I wish there was a way to do version greater than / less than queries. But I can't think of anything in Notion that would provide that.
There was a problem hiding this comment.
How sensitive is this to manipulations to the table? It might be possible to use a formula in a manually-created column but would that confuse the plugin?
There was a problem hiding this comment.
Custom columns seem to work fine. As long as their names don't conflict with what's in this list.
joshuapease
requested review from
ten1seven,
maxdmyers,
maxfenton and
JJimmyFlynn
| self::PROPERTY_PLUGINS => [ | ||
| 'class' => MultiSelectDb::class, | ||
| ], | ||
| self::PROPERTY_PLUGIN_VERSIONS => [ | ||
| 'class' => MultiSelectDb::class, | ||
| ], |
There was a problem hiding this comment.
How sensitive is this to manipulations to the table? It might be possible to use a formula in a manually-created column but would that confuse the plugin?
I switched the majority our site properties over to Select and MultiSelect properties.
This makes it so we can more easily filter: