-
Notifications
You must be signed in to change notification settings - Fork 54
Adding support for minimum number of Fieldsets #249
Comments
+1 |
1 similar comment
+1 |
I may have recently had the need for this as well. So if I get a chance I'll add this functionality. I'm thinking besides just raw number of fieldsets, the type might be considered as well in the use-case of multiple fieldsets. |
+1 |
2 similar comments
+1 |
+1 |
+1 |
2 similar comments
+1 |
+1 |
It would be great to just add the minimum number first to get it in there quickly, and then evolve it to support deeper inspection. Just sayin! |
@argentini (and everyone else) I've got a working feature branch for this. It validates the number of enabled fieldsets against a configurable minimum number of fieldsets. When we get around to creating a new release, this will probably go in there. |
Nice 😁 |
@kjac Is the feature branch on remote by chance? I ran into a need for minimum fieldsets lately and was thinking of having a go at it. I looked through your fork and here, but didn't see any branches with recent work on them for minimum fieldsets. |
@kelvinschutz I have it in my local repo. I'm on vacation at the moment... will submit a PR as soon as I can, probably next week. |
@kjac That's awesome! Let me know if there is any way I can assist :) |
@kelvinschutz I'm going to play around with Archetype the next few days, it should be ready shortly. Here's a sneak preview: /cc @kgiszewski |
@kjac Epic! Looks awesome already 👍 |
@kjac This is excellent! |
Added in v1.15.1 |
Next to the option of the max number of fieldsets it would be awesome to have a minimum also. Great to force a specific number of fieldsets when the design desires this.
The text was updated successfully, but these errors were encountered: