-
Notifications
You must be signed in to change notification settings - Fork 147
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
Constructors question #132
Labels
Comments
Very good question. |
Should we tag the current status as a new version? |
@wittfabian I believe that we should rewrite the code, tbh an important thing to do is parsing the request array within the class and fetch the data accordingly. It's super messy and weird to use arrays with index 0 to access data etc.. |
Are you going to maintain compatibility in class constructors? |
I wouldn't think so. Time consuming and complicated. Parameters would be
the same but required within a key value array instead.
On Sun, Mar 4, 2018 at 3:25 AM Arsen Goian ***@***.***> wrote:
Are you going to maintain compatibility in class constructors?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#132 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEP0mLey-sG7Tp29ylJ3EMLdkVyb5Xryks5tavwygaJpZM4SRQ-D>
.
--
* Jason Shaw <[email protected]>*, Developer
Tel. 647 783 7463 | Skype: jason.engage
en.gg | <http://en.gg/>Follow me on Facebook
<http://www.facebook.com/engagetheweb>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey Fabian, what's your opinion on making constuctors?
At the moment, we have a series of parameters - and they are getting out of order.
Should a constructor just accept an array instead? Should that be how 2.0 works?
The text was updated successfully, but these errors were encountered: