Our state of the art Gantt chart


Post by miro »

Regarding the purpose of the versioning feature, do we need to save it to the database or not? if yes, how about the structure of the database of versioning and is there is an example of .net core that can be leveraged? Any option to hide or appear this versioning feature, because it thems to be enable or On all the time and ideally if there is a way to make it appear or disappear as required.


Post by emil »

Hi Miro,

The versions feature can be used within a single user's session without persisting anything to your database. If you would like versions to be stored between sessions then you do need to persist them. Attached is a diagram of the class structure.

The extent to which you choose to mirror this structure in your own DB is a decision for you to make. You might choose to fully normalize these entities in your DB, or store versions simply as JSON blobs, for example. Note that versions and all of their contents (transactions, actions, etc.) are intended to be immutable.

There is no .NET-specific example at this time.

The versions feature, like other features, can be enabled and disabled, assuming you already specified it in the features of your Gantt's configuration:

// enable versions
gantt.features.versions.disabled = false;

In terms of visually appearing/disappearing, the UI we provide for this feature is found in the VersionGrid component, and it's up to you whether and when you show that.

Thanks,

Emil

Attachments
versions-class-diagram.png
versions-class-diagram.png (308.5 KiB) Viewed 78 times

Post Reply