-
Notifications
You must be signed in to change notification settings - Fork 28
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
Fieldtype values editing support #85
Conversation
53e7bac
to
a710831
Compare
public function theEditFormShouldContainAFieldsetNamedAfterTheFieldDefinition() | ||
{ | ||
$this->assertElementContainsText( | ||
sprintf('div.ezfield-identifier-%s fieldset legend', self::$fieldIdentifier), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The selector can be used without the div
+1 |
No real need to +1 the whole PR yet, as the topic branches aren't merged yet. But I'll take that as a +1 on the BDD :-) |
* EZP-25775: Checkbox content edition support
A FormTypeBasedFieldValueFormMapper is added. It comes with an abstract ezrepoforms.field_type.form_mapper.form_type_based service. It can be used to map fieldtype values when no particular configuration is required, and a single fieldtype is used (primitive or custom).
The service tag ez.fieldType.formMapper is deprecated, and splitted into ez.fieldFormMapper.value and ez.fieldFormMapper.definition. The dispatcher pass & dispatcher are updated to distinguish both while still being backward compatible.
…dit_support User FieldType content edit support (EZP-27530)
* Fix EZP-25776: Selection content edition support * Fix content type of behat context not being reloaded after updating the field definition.
All todos taken care of, and tests are passing. I suggest we merge this, what do you think @glye ? |
I say not nay, I say aye! 🎩 |
And here we merge. |
Contents
BDD coverage for User (will fail until implementation is merged from #83) and TextLine fieldtypes(moved to #83)Other pull-requests