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's currently possible to enable/disable fields.
That will be reflected on the isActive column in the fieldMetadata table of the metadata schema.
We're about to create new columns for standard objects (e.g. "description" column on company)
But we don't want to create too many columns or pollute existing workspace with column people didn't ask for.
So we need to adapt the decorator for this (fields will be created by disabled by default).
Implementation
We should allow for a new decorator parameter on the FieldMetadata decorator:
@FieldMetadata({
type: FieldMetadataType.TEXT,
label: 'Name',
description: 'The company name',
icon: 'IconBuildingSkyscraper',
isActive: false
})
It could also be its own decorator @isInactive but I feel like it would mean it's always inactive like isNullable or isSystem, while label, description, icon etc are already also values that can be edited by the user.
@magrinj what option do you prefer between the two?
The text was updated successfully, but these errors were encountered:
Hi @FelixMalfait
Please assign me this issue and could you please tell me which dir should I explore first? Sorry its my first backend issue soon I'll get comfortable with it like frontend
@FelixMalfait Sorry for the delay, I didn't see the ping on this ticket, adding @IsInactive decorator sounds good to me if by default they are active, but it's maybe more readable adding it to the @FieldMetadata decorator for now
Context
It's currently possible to enable/disable fields.
That will be reflected on the
isActive
column in thefieldMetadata
table of themetadata
schema.We're about to create new columns for standard objects (e.g. "description" column on company)
But we don't want to create too many columns or pollute existing workspace with column people didn't ask for.
So we need to adapt the decorator for this (fields will be created by disabled by default).
Implementation
We should allow for a new decorator parameter on the
FieldMetadata
decorator:It could also be its own decorator
@isInactive
but I feel like it would mean it's always inactive likeisNullable
orisSystem
, while label, description, icon etc are already also values that can be edited by the user.@magrinj what option do you prefer between the two?
The text was updated successfully, but these errors were encountered: