We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello,
Entries are read-only, which is clearly stated in documentation.
What do you think about marking following \Schematic\Entry variables as protected?
\Schematic\Entry
This way I can extend class and update values without generating new object for each update.
Would you even consider this type of change? Are there any potential drawbacks?
Thanks in advance for your answer.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello,
Entries are read-only, which is clearly stated in documentation.
What do you think about marking following
\Schematic\Entry
variables as protected?This way I can extend class and update values without generating new object for each update.
Would you even consider this type of change?
Are there any potential drawbacks?
Thanks in advance for your answer.
The text was updated successfully, but these errors were encountered: