-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
yii2 现在进行的如何? #1
Comments
Meh, you snatched the first issue number :-) |
yes!We all want to know yii2 trend |
= =!好久没弄PHP了,看到YII2的消息,过来打个酱油 |
打酱油来也,正在学习YII! |
guys!Tell yii team we are looking forward to. |
Мы из России народ простой :) По вашему не бум бум. Тоже желаем знать когда же, когда? |
Да да да :) |
На форуме yii они иногда выкладывают часть исходников |
We want a complete package of yii, |
We don't have estimates but working on it as hard as possible. https://github.com/yiisoft/yii2/wiki/Yii2-Development-Roadmap |
Why not let yii2 open it, so we can know your work and to what extent, |
samdark commented 17 minutes ago https://github.com/yiisoft/yii2/wiki/Yii2-Development-Roadmap Thanks for the information and hard work. |
We'll open alpha state code when it will be ready and then will continue to improve it. |
Yii is and always was semi open source (non-real) project, so current core team behavior/point was known in advance before second version development started. Yii is a great framework but closed alpha development process contradicts to the true open source postulates. Using OSI and FSF approved licenses doesn't mean anything. All that is left to do is to wait. |
@resurtm True |
It might be open source but it's not community written, it's community contributed. If they opened it now it would be a frenzy of pull requests / feature requests for stuff that's still half way through building. It would also mean people start forking way too early in the project and develop in an entirely new direction on there own (which there's nothing wrong with) but then still expect support. I appreciate these guys are designing and building the best they can until it's at a point where it can be used safely. Anything beyond that is features and bugs, rather than core design work. |
@paystey True |
With the state the code is in right now it's not going to be any use to anyone, it just adds more overhead to developing it. Although I can understand the need to see the code, I would prefer to see a few more updates from maintainers too as we get closer to alpha release. We're on the outside looking in and have no idea what to expect, whether to plan to move because changes are do able, features we should hold off building ourselves because they're in 2.0, etc. So I'm in favour of a more documented development of Yii 2.0 rather than showing us the code and us ripping it apart. |
I don't agree so much. |
It's a false arguments. Take a look at the Symfony2 development process: it's open since first commit (https://github.com/symfony/symfony/tree/65d075016888e202cc20c9710800512caec77811), but there wasn't pull request frenzy and any other difficulties. Keep in mind that Symfony far more popular than Yii. :-)
What kind of expected support are you talking about? Core developers never supported third party forks and development versions. |
@resurtm +1 |
@callmez I'm all for suggesting features, and I think they should document what they're doing a little more. It's all just a black box at the minute. I'd like to know which bits are improving, what's changing, how backwards compatible some things are etc. even a simple Blog would do a lot of good. @resurtm I see no good reason that anybody needs the code right now. It would be nice to know features etc. but the amount of overhead it would add to development time dealing with prealpha code, requests, "helpers" is just not worth it. Get alpha done, get the code out, see what everyone thinks, then either restart or work towards beta as a community. I trust these guys to get the core principles right, and if that means undisturbed then so be it. |
I agree with @paystey. I think both sides of the discussion have a point, but considering how much time the dev team puts into this, then if this is how they want to do it we should respect that. The pre-alpha openness or not probably won't affect the end result very much anyway, so let them create the alpha as they please and then we can all chime in and make it even better during alpha stage. Remember, alpha is very early in the process, there will be plenty if time to provide feedback and suggestions. Also, FWIW, there has (since long) been forum discussions in the Yii forum about core features för Yii2, so people have already had a chance to give feedback and affect the alpha development process. If you weren't there at that point, perhaps you were not paying enough attention (that is a comment from me personally, not the Yii project, in case the statement upsets anyone, and it's also just a reflection, I'm not trying to offend anyone with it). For example there was a change in the logging feature due to a discussion I had with the core developers there, so there has definately been room for affecting how Yii2 should look to some extent. At the end of the day, big deal. It's not like the project is closed source. |
In China, there are many yii supporters. Now the question is difficult to master it quickly and learning coupled with high costs. |
Now! 下班!!!! |
GitHub is not the right place to discuss about this. There is an active forum for Design Discussions for Yii 2.0: http://www.yiiframework.com/forum/index.php/forum/42-design-discussions-for-yii-20/ If you have suggestions, you can post them there. |
method quoteValue() in framework/db/Schema.php ``mb_stripos(): Passing null to parameter yiisoft#1 ($haystack) of type string is deprecated``
PHP 8.1 trim(): Passing null to parameter yiisoft#1 ($string) of type string is deprecated
`mb_stripos(): Passing null to parameter #1 ($haystack) of type string is deprecated`
… string is deprecated yiisoft#19684
…) of type string is deprecated
…cated: mb_strlen(): Passing null to parameter #1 ($string) of type string is deprecated
fixing: trim(): Passing null to parameter yiisoft#1 ($string) of type string is deprecated on PHP 8.2
PHP 8.1 trim(): Passing null to parameter #1 ($string) of type string is deprecated
* added pcntl to requirements check * Fix #13920: Fixed erroneous validation for specific cases * Fix #13920: Added my name to CHANGELOG.md * trim(): Passing null to parameter #1 ($string) of type string is deprecated * Added section about Unsafe Reflection in Security best practices doc (#19948) Co-authored-by: Bizley <[email protected]> * Update CHANGELOG.md * Fixed tests. * Fix #13920: Add unit test * Update `bower-asset/inputmask`, `bower-asset/punycode`. * added CHANGELOG line * Fix order. * fix: #19978 - Mistake in Korean translation * fix: keep doublequote * Do not duplicate log messages in memory * Update framework/log/FileTarget.php Co-authored-by: Bizley <[email protected]> * Update concept-di-container.md Сслка "Конфигурация приложения" была не верной, она вела на страницу "Service-locator'a" * Update CHANGELOG.md * release version 2.0.49.1 * prepare for next release * Revert changes in `mimeTypes.php` from 4a1f2c6 restores #19936 * update actions/checkout to v4 * Fix mime type generator * Added note * Update structure-controllers.md (#20003) добавил пропущенное слово "как" * Update CHANGELOG.md 2.0.49.2 changelog * release version 2.0.49.2 * prepare for next release * New methods: BaseActiveRecord::loadRelations() and BaseActiveRecord::loadRelationsFor(). * Fixed a bug where the yii serve command would break if a custom router was supplied and it had a space in the path * Fix `MaskedInputAsset::class`. * Fix #19927: Fixed `console\controllers\MessageController` when saving translations to database: fixed FK error when adding new string and language at the same time, checking/regenerating all missing messages and dropping messages for unused languages * Added 'zh' into 'framework/messages/config.php' (#19995) --------- Co-authored-by: Tobias Munk <[email protected]> Co-authored-by: Tim Fischer <[email protected]> Co-authored-by: Tim Fischer <[email protected]> Co-authored-by: Alexander Makarov <[email protected]> Co-authored-by: Oleg Poludnenko <[email protected]> Co-authored-by: Bizley <[email protected]> Co-authored-by: Sonia Zorba <[email protected]> Co-authored-by: Tobias Munk <[email protected]> Co-authored-by: Akbar Herlambang <[email protected]> Co-authored-by: lubosdz <[email protected]> Co-authored-by: Yuriy Bachevskiy <[email protected]> Co-authored-by: Robert Korulczyk <[email protected]> Co-authored-by: salehhashemi1992 <[email protected]> Co-authored-by: PowerGamer1 <[email protected]> Co-authored-by: Brad Bell <[email protected]> Co-authored-by: Alexandru Trandafir Catalin <[email protected]> Co-authored-by: Nabi KaramAliZadeh <[email protected]>
Exception 'TypeError' with message 'count(): Argument yiisoft#1 ($value) must be of type Countable|array, bool given'
PHP Deprecated Warning 'yii\base\ErrorException' with message 'trim(): Passing null to parameter yiisoft#1 ($string) of type string is deprecated' in /app/shop.box/vendor/yiisoft/yii2/validators/FilterValidator.php:81
好像了解下yii2的情况, 目前已经完成多少.为何不释出让大家看看.也能讨论下yii2的需求.
哎哟不错哟.沙发,哈哈!希望别关掉了...
The text was updated successfully, but these errors were encountered: