Skip to content
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

Partial helper pull vars from view model #329

Merged

Conversation

hungtrinh
Copy link

Close #328

Explained root cause here #328 (comment).

Solution

check if second param of partial helper has method getVars then use this method to pull model data for partial script

@hungtrinh
Copy link
Author

Mr @glensc could you please review this PR, thanks.

@hungtrinh hungtrinh changed the title Close 328 - BC partial inheritance vars from view model Close 328 - partial helper pull vars from view model Feb 24, 2023
@glensc
Copy link
Collaborator

glensc commented Feb 27, 2023

  1. close keywords belong to pr body. remove from title

@hungtrinh hungtrinh changed the title Close 328 - partial helper pull vars from view model Partial helper pull vars from view model Feb 27, 2023
@hungtrinh
Copy link
Author

  1. close keywords belong to pr body. remove from title

Mr @glensc removed close keyword from title

@glensc glensc merged commit c098449 into Shardj:master Feb 27, 2023
falkenhawk added a commit to zf1s/zf1 that referenced this pull request Jan 3, 2024
It looks like it's safe to use the `#[AllowDynamicProperties]` attribute, and it should still be valid for php 9.0 and not throw an error, contrary to what I understood at first.

As per RFC:
https://wiki.php.net/rfc/deprecate_dynamic_properties#proposal
"The creation of dynamic properties on classes that aren't marked with the #[AllowDynamicProperties] attribute is deprecated in PHP 8.2 and becomes an Error exception in PHP 9.0."

Related issues from zf1-future where they went with refactoring those classes to use a defined property to store all previously dynamic props in an array, which introduced breaking changes:
Shardj/zf1-future#307 (comment)
Shardj/zf1-future#261
Shardj/zf1-future#268
Shardj/zf1-future#328
Shardj/zf1-future#329
falkenhawk added a commit to zf1s/zend-form that referenced this pull request Jan 4, 2024
It looks like it's safe to use the `#[AllowDynamicProperties]` attribute, and it should still be valid for php 9.0 and not throw an error, contrary to what I understood at first.

As per RFC:
https://wiki.php.net/rfc/deprecate_dynamic_properties#proposal
"The creation of dynamic properties on classes that aren't marked with the #[AllowDynamicProperties] attribute is deprecated in PHP 8.2 and becomes an Error exception in PHP 9.0."

Related issues from zf1-future where they went with refactoring those classes to use a defined property to store all previously dynamic props in an array, which introduced breaking changes:
Shardj/zf1-future#307 (comment)
Shardj/zf1-future#261
Shardj/zf1-future#268
Shardj/zf1-future#328
Shardj/zf1-future#329
falkenhawk added a commit to zf1s/zend-view that referenced this pull request Jan 4, 2024
It looks like it's safe to use the `#[AllowDynamicProperties]` attribute, and it should still be valid for php 9.0 and not throw an error, contrary to what I understood at first.

As per RFC:
https://wiki.php.net/rfc/deprecate_dynamic_properties#proposal
"The creation of dynamic properties on classes that aren't marked with the #[AllowDynamicProperties] attribute is deprecated in PHP 8.2 and becomes an Error exception in PHP 9.0."

Related issues from zf1-future where they went with refactoring those classes to use a defined property to store all previously dynamic props in an array, which introduced breaking changes:
Shardj/zf1-future#307 (comment)
Shardj/zf1-future#261
Shardj/zf1-future#268
Shardj/zf1-future#328
Shardj/zf1-future#329
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Partial behaviour changed
2 participants