-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
not merge this is a proposal #92
base: master
Are you sure you want to change the base?
Conversation
I think the idea of keeping everything in a view is very good because it is more user friendly, however it is difficult to do tests, I think it would be better to design, follow the CRUD convention. I mention it to continue doing the tests what do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👏 👏 PR Review 👏 👏
I like your approach. But there are some things that need to be changed a bit.
I won't be able to give time to this project tomorrow since I'll be a bit busy. I'll discuss it here as soon as I can. Be patient and thanks for your time and help that you are contributing so generously 👏 .
Yes we have to follow CRUD convention, it will make the code more readable, but all these will do a major change in, so it's the perfect time to do this. |
I will create a new dev branch to push any new changes before merging on Master branch. We need to follow 1 step at a time for this big refactoring. What do you think? |
@changeweb yes it's the perfect way. step at a time, what would you think is the easiest first step? |
We should do something like this:
|
@changeweb today I have time if you can create a new branch, I'll start like you told. |
@JuanVqz ok I'm creating one |
@JuanVqz |
@changeweb sorry for many problems. We should set the format of the name of the style attributes, I think it's easier to read with the case of the snake, for example, I think we can follow this guide or maybe all guide naming conventions I don't like this format maybe only in classes it's good. public function foo()
{
//
} I'm like this format public function foo() {
//
} but you should set the format... |
I try to use snake case for variable name and camel case for function name. Some variable names got camel cased because I read an article about snake case vs camel case and wanted to see how it looks when implemented. But I got lazy to update them later. Sorry. |
These are PHP Coding Standard, so we should stick to them |
sorry typo. I meant to reference 192 not 92 |
I think the idea of keeping everything in a view is very good because
it is more user friendly, however it is difficult to do tests,
I think it would be better to design, follow the CRUD convention.
I mention it to continue doing the tests
what do you think?