-
Notifications
You must be signed in to change notification settings - Fork 333
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge SiteTreeURLSegmentField and SegmentField #2786
Comments
NOTE: The segment field derivative seems more useful than just the way CMS uses it. It should probably be put in framework or admin, so projects which don't use this module can take advantage of it. |
If this looks like it's going to take more than a day drop it. |
Will close issue without doing work |
I would still like this to happen in some way even if it's not in CMS5. |
There's SiteTreeURLSegmentField in the CMS module and a derivative SegmentField in its own module. The derivative is used by UserForm.
SegmentField
seems generally better in every way and is more flexible since it allows you to use it for anyDataObject
.Acceptance criteria
silverstripe/segment-field
.Notes
The text was updated successfully, but these errors were encountered: