You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Changed `Phalcon\Support\HelperFactory` to use the internal mapper for better memory management [#16571](https://github.com/phalcon/cphalcon/issues/16571)
8
+
9
+
### Added
10
+
11
+
- New ini setting `phalcon.form.strict_entity_property_check` for `Phalcon\Forms\Form` to enable strict entity property checking. [#16567](https://github.com/phalcon/cphalcon/issues/16567)
12
+
13
+
### Fixed
14
+
15
+
- Fixed `Phalcon\Mvc\Cli\Router` to extend the `Phalcon\Mvc\Cli\RouterInterface`[#16551](https://github.com/phalcon/cphalcon/issues/16551)
16
+
- Fixed `Phalcon\Filter\Validation\Validator\StringLength::validate()` to correctly use the `include` parameter [#16560](https://github.com/phalcon/cphalcon/issues/16560)
17
+
- Fixed `Phalcon\Db\Column::TYPE_BINARY` and `Phalcon\Db\Column::TYPE_TINYINTEGER` to have unique values [#16532](https://github.com/phalcon/cphalcon/issues/16532)
18
+
- Fixed `Phalcon\Forms\Form` to bind only existing properties on entities, based on `phalcon.form.strict_entity_property_check` setting. [#16567](https://github.com/phalcon/cphalcon/issues/16567)
19
+
- Fixed `Phalcon\Filter\Sanitize\BoolVal` to correctly handle integers. [#16582](https://github.com/phalcon/cphalcon/issues/16582)
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,13 +15,12 @@ We use the GitHub issues for tracking bugs and feature requests and have limited
15
15
16
16
_Please use the [Documentation](https://phalcon.io/docs) before anything else. You can also use the search feature in our documents to find what you are looking for. If your question is still not answered, there are more options below._
17
17
18
-
* Questions should go to [Official Forums](https://phalcon.io/forum)
18
+
* Questions should go to [GitHub Discussions](https://phalcon.io/discussions)
19
19
* Another way is to ask a question on [Stack Overflow](https://stackoverflow.com/) and tag it with
* Come join the Phalcon [Discord](https://phalcon.io/discord)
22
22
* Our social network accounts are:
23
23
*[Telegram](https://phalcon.io/telegram)
24
-
*[Parler](https://phalcon.io/parler)
25
24
*[Gab](https://phalcon.io/gab)
26
25
*[MeWe](https://phalcon.io/mewe)
27
26
*[Twitter](https://phalcon.io/t)
@@ -42,13 +41,13 @@ Please report bugs when you've exhausted all of the above options.
42
41
43
42
* Don't submit your pull requests to the `master` branch. Branch from the required branch and, if needed, rebase to the proper branch before submitting your pull request. If it doesn't merge cleanly with master you may be asked to rebase your changes
44
43
* Don't put submodule updates in your pull request unless they are to landed commits
45
-
* Add tests relevant to the fixed bug or new feature. Test classes should follow the [PSR-2 coding style guide](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md). See our [testing guide](https://github.com/phalcon/cphalcon/blob/master/tests/README.md) for more information
44
+
* Add tests relevant to the fixed bug or new feature. Test classes should follow the [PSR-12 coding style guide](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-12-coding-style-guide.md).
46
45
* Phalcon is written in [Zephir](https://zephir-lang.com/), please do not submit commits that modify C generated files directly or those whose functionality/fixes are implemented in the C programming language
47
46
* Remove any change to `ext/kernel`, `*.zep.c` and `*.zep.h` files before submitting the pull request
48
47
49
48
## Requesting Features
50
49
51
-
If you have a change or new feature in mind, please fill a [NFR](https://docs.phalcon.io/latest/new-feature-request) on the GitHub. Alternatively you may also request features via [the FeatHub page](https://feathub.com/phalcon/cphalcon).
50
+
If you have a change or new feature in mind, please fill a [NFR](https://docs.phalcon.io/latest/new-feature-request) on the GitHub.
0 commit comments