MVC and the business rule
I need to know where in the MVC should I apply the business rule.
Access public property of object on view
When we are working with some MVC FW on PHP, generally we have a view loading function like load(string viewName, optional array viewVariables). My doubt here is: if we are working with some object, like a table row result, we need pass this object entirely to view or we need pass only what will be need on view?
Access public property of object on view
When we are working with some MVC FW on PHP, generally we have a view loading function like load(string viewName, optional array viewVariables). My doubt here is: if we are working with some object, like a table row result, we need pass this object entirely to view or we need pass only what will be need on view?
Access public property of object on view
When we are working with some MVC FW on PHP, generally we have a view loading function like load(string viewName, optional array viewVariables). My doubt here is: if we are working with some object, like a table row result, we need pass this object entirely to view or we need pass only what will be need on view?
Access public property of object on view
When we are working with some MVC FW on PHP, generally we have a view loading function like load(string viewName, optional array viewVariables). My doubt here is: if we are working with some object, like a table row result, we need pass this object entirely to view or we need pass only what will be need on view?
Access public property of object on view
When we are working with some MVC FW on PHP, generally we have a view loading function like load(string viewName, optional array viewVariables). My doubt here is: if we are working with some object, like a table row result, we need pass this object entirely to view or we need pass only what will be need on view?
Exception class for each exception or for all framework
I am developing a framework and it can generate various types of exceptions. Initially I’m working with a single exception class that indicates that something went wrong inside the framework. However, I was thinking, maybe it would not be correct to create a specific class for each specific type of exception?
Exception class for each exception or for all framework
I am developing a framework and it can generate various types of exceptions. Initially I’m working with a single exception class that indicates that something went wrong inside the framework. However, I was thinking, maybe it would not be correct to create a specific class for each specific type of exception?
Exception class for each exception or for all framework
I am developing a framework and it can generate various types of exceptions. Initially I’m working with a single exception class that indicates that something went wrong inside the framework. However, I was thinking, maybe it would not be correct to create a specific class for each specific type of exception?
Exception class for each exception or for all framework
I am developing a framework and it can generate various types of exceptions. Initially I’m working with a single exception class that indicates that something went wrong inside the framework. However, I was thinking, maybe it would not be correct to create a specific class for each specific type of exception?