You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to be able to hide enums with an extra flag in the schema.
In my case I have enums like locale that are used a bit everywhere, and make the diagram generated really messy.
I would like to keep table, the fields and their relations, just ignore the enums.
Could be implemented in multiple ways:
an ignoreEnums flag, similar to the tableOnly flag
an ignoreTables list, allowing to hide any table or enums manually. Could be useful to also hide some "technical" tables (logs, revisions, ...)
Issue
I found a previous issue about it: #120
But it was closed few months ago and I can't find any commit or documentation related to that. tableOnly is partially doing it, but it's two different things and in my case tableOnly is not what I'm looking for.
The text was updated successfully, but these errors were encountered:
66d2d07 commit looks related. Their example shows a status enum that isn't being included when you use the tableOnly mode. It also hides all the table attributes. Or should at least. It should be relatively easy to move that hiding of enums out to another config param.
Would you be interested in making that change? If not you'll need to wait for me to prioritize it.
Description
It would be nice to be able to hide enums with an extra flag in the schema.
In my case I have enums like
locale
that are used a bit everywhere, and make the diagram generated really messy.I would like to keep table, the fields and their relations, just ignore the enums.
Could be implemented in multiple ways:
ignoreEnums
flag, similar to thetableOnly
flagignoreTables
list, allowing to hide any table or enums manually. Could be useful to also hide some "technical" tables (logs, revisions, ...)Issue
I found a previous issue about it: #120
But it was closed few months ago and I can't find any commit or documentation related to that.
tableOnly
is partially doing it, but it's two different things and in my casetableOnly
is not what I'm looking for.The text was updated successfully, but these errors were encountered: