Object Type data parsing for the blade template #7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added object parsing support for the blade view function
Description
Added object parsing support for the blade view function, the view and render functions are explicitly set to receive the $data parameter as of type array, which is also fine but it's not very presentable when have very little or very large amount of data.
So I modified the $data parameter in the
view
andrender
function to also receive objects, if the then received data is object it is converted to array.Comparison between array and object passing as data in the view function
While this could be subjective from user to user, I think the data passed as an object look more presentable and are less congested.