This repository has been archived by the owner on Mar 1, 2023. It is now read-only.
[FEATURE] add getter getInstances() in FormObjectFactory #87
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Following the commit 2f23f80, a field validator should be instantiated with the object manager, to allow more Extbase feature. The instantiation type was not modified in the Ajax controller, though.
This allows more flexibility for the messages initialization; for instance you can dynamically build the messages list in the method `initializeObject()` of your validator, then they will be processed just before the validation actually runs.
Fluid variables were not passed correctly to the layout standalone view of a field. This commit fixes this issue, as well as a refactor for the older versions behaviour to make the code more readable.
A collision could occur on the name of the asset files for two forms with the same definition but with different names.
The message template of a field can be filled with the same marker several times: every occurrence should be replaced. Example: ``` messageTemplate = <span class="#TYPE#" data-#TYPE#="bar">#FIELD#</span> ```
On an ajax call, FormZ will get all the input in the form tag and will create the query. But if there is an input unformatted (without `[]`) FormZ will send a bad data.
It allows for instance nesting several fields located in multiple partial files.
Allows the inner part of a slot to have access to the current view variables.
Fixes an issue in TYPO3 v8 where rendering a partial or using a layout was impossible due to the inheritance of layout/partial root paths not properly set.
Couple of fixes that will fix certain issues when working with nested fields in TYPO3 v8.
After StyleCI inspection failed.
Allow some more characters, mostly for German language. Fixes #76
When any field starts its validation, the data attribute `fz-loading` is added to the `<form>` tag. When the validation is done (successful or not) the data attribute is removed.
Removing beginning/ending whitespaces on input fields.
Can be used to check whether a field does contain any value (it is not empty).
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.