View source for Supporting SEF URLs in your component

=== A more complex Example === <!--T:58-->
</translate>

<translate><!--T:59--> This more complicated example will illustrate the basics of implementing a more custom router for your component.</translate>

<source lang="php">
use Joomla\CMS\Component\Router\RouterBase;

class [componentname]Router extends RouterBase
{
    public function build(&$query)
    {
        $segments = array();
        if (isset($query['view']))
        {
            $segments[] = $query['view'];
            unset($query['view']);
        }
        if (isset($query['id']))
        {
            $segments[] = $query['id'];
            unset($query['id']);
        };
        return $segments;
    }
</source>

<translate><!--T:60--> <code>\Joomla\CMS\Router\Router</code> passes a <code>$query</code> array to the <code>[''componentname'']Router::build</code> function. This function will add the relevant parts of the array to the $segments array in the right order and will return the properly ordered array. The content of the <code>$query</code> array needs to be unset, otherwise <code>\Joomla\CMS\Router\Router</code> will add it to the URL in the form of a query string (i.e. any variables that are not handled by the router will be passed in the query string).</translate>
<translate>
<!--T:61-->
Note in the above we have chosen to extend <code>\Joomla\CMS\Component\Router\RouterBase</code> as we do not need to do any preprocessing in this simple example.</translate>

<translate><!--T:62--> The prefix ''componentname'' is the name for your component, as found in the directory holding the component's files. For instance, a component "Magic" in directory <tt>/components/com_magic/...</tt> would use a prefix <code>magic</code> (all lower case).</translate>
<translate>
<!--T:63-->
The next function in the <tt>router.php</tt> parses the URL:</translate>

<source lang="php">
public function parse(&$segments)
{
    $vars = array();
    switch($segments[0])
    {
        case 'categories':
            $vars['view'] = 'categories';
            break;
        case 'category':
            $vars['view'] = 'category';
            $id = explode(':', $segments[1]);
            $vars['id'] = (int) $id[0];
            break;
        case 'article':
            $vars['view'] = 'article';
            $id = explode(':', $segments[1]);
            $vars['id'] = (int) $id[0];
            break;
    }
    return $vars;
}
</source>

<translate><!--T:64--> What happens here? In the function <code>[''componentname'']Router::build</code> we arranged the items in the <code>$query</code> array in a specific sequence. This means that in this example the view is first and the id is second in the array.</translate>

<translate><!--T:65--> By reading <code>$segments[0]</code>, we access the name of the view. We set the right view and/or identifier depending on its value and we return the <code>$vars</code> array to <code>\Joomla\CMS\Router\Router</code>. <code>$vars</code> should be an associative array similar to the array that was passed to the BuildRoute method.</translate>

<translate><!--T:66--> The above example of the <tt>router.php</tt> is a very simple way to generate SEF URLs but should show how this works quite clearly.</translate>
<translate>
<!--T:67-->
The generated URL in this example contains the name of the view and doesn't reflect the content hierarchy:</translate>

<tt><nowiki>http://www.example.com/[menualias]/[view]/[slug]</nowiki></tt>

<translate>