Conditional fields rendering and fields grouping.

[SnapeEye]

Hi there!

I'm trying to make a POC for my app. And I want to use this builder for part of it.
But I have some issues/questions here.

• Conditional fields rendering

As far as I understand, the only possible way to do it is via shouldBeProcessed method that can be declared in createEntity.
Potentially, it may work. But the available arguments seem to be quite limited.

For example, I created an attribute "rules" where I will gather some rules/conditions/comparisons that should define whether to display other fields. Like: hide -> fields(-s) -> if current field's value -> is/is not -> some comparison value.

But here is a catch: as rules is going to be an attribute - many rules, which actually may affect current field, may be stored in attributes of different fields. But shouldBeProcessed only provides entitiesValues (btw, ONLY of the same type as current entity) and entity (current processing entity). So that it is impossible to access rules attribute of all the fields.

My question: is there any convenient/correct/possible way to handle this?
Because currently, the only solution is to add an extra argument for shouldBeProcessed - schema. schema is going to provide all fields and their attributes, so that it will make possible to access all the rules and then decide whether current fields should be processed. But, of course, this should be added to the lib.

• Fields grouping

In doc, I found some code sample where some section fields is used. But there is actually no actual example of that component code.
IMHO, this is one of the most important parts for builder. As the current "demo" on the website does not show this. Also, I guess it'd require to improve dnd to support such entity.

My question: is there any real example of section entity (especially with dnd)?

[sandulat]

Hi @SnapeEye!

Conditional fields rendering

You're right, shouldBeProcessed and similar methods should include as much context as possible, beyond just the entity values. In fact, I'm already working on this following a similar discussion that took place on our Discord.

Fields grouping

I don’t have any live examples of grouping at the moment, but this should be fairly straightforward to implement using the following methods on your builder store:

• setEntityParent – Sets an entity’s parent. You can also specify the index at which to place it within the parent.
• unsetEntityParent – Removes the entity’s parent and moves it to the root. You can also specify the index at which to place it within the root.
• addEntity – Adds a new entity. You can optionally provide a parent ID and an index to position it within the parent or in the root if no parent ID is provided.

Are you running into any specific issues with grouping? Feel free to share your code and I’ll do my best to help out.

Right now, I’m focused on releasing a v1.0 candidate based on community feedback and personal observations. This release will include your shouldBeProcessed request as well. After that, I’ll be adding multiple live examples of various builder setups in the docs, including field grouping with DnD and more. I’ll keep you posted!

[SnapeEye]

Sounds promising!

Just for context, are there any plans when a v1 is about to be live?

[sandulat]

@SnapeEye I'll do my best to have a release candidate ready in the coming weeks. Unfortunately I got hit by the flu, so there will be a slight delay.