Dynamic Router Implementation #74
Labels
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: joomla/Component-Builder#74
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I just looked at the code for the contact router concept and I like it 👍
How to improve the JCB router code without breaking exiting implementation.
I will need help from you who know more about this aspect. We need to start moving this into the new direction to be ready for Joomla v4.
Okay the code that builds the router details are found in a few places. I want to update this, but will need some help.
Since we need to combine many site views and filters into this it is very hard to make it dynamic. But we have to try.
Methods
The compiler deals with this in the following places:
Files
The files used to build the router
We can adapt any of these.
@ro-ot I am not so familiar with this part and can do with some help! @stutteringp0et How is your take on the router, can you help? This seems to be urgent!!
My investigation has revealed some interesting issues! Mostly that we already have a great and stable implementation that should still work without issues. Well so it seems anyway.
What seems to be the issue is that the compiler needs some tweaking in routerParseSwitch since it loads the wrong values and that is why we are seeing issues in the router at this time.
I will dig little deeper and keep you posted.
Looks like the only way to make this as dynamic as we need, I will have to add some fields to the dynamicGet where you can override the router.
Two new PHP fields
parse
methodbuild
methodStill playing with some ideas, any feedback will be helpful.
I agree that adding a field to JCB to allow more customization, but not in the dynamicGet area, but instead in the site view. Unless you also add dynamic placeholders for the site view code name.
Only one field really is needed targeting the parse method, allowing you to only adapt the snippet in the switch.
Great Work!
I found that!