need to be able to specify multiple active paths
See original GitHub issue<a href="/hello/user" use:link use:active={'/hello/*'}>Say hi with a default className!</a>
I want to set it active for /hello
and /hello/*
. Doing /hello*
doesn’t work
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
What is the order of precedence when there are multiple ...
I am just wondering what the order of precedence is when multiple Spring active profiles have been specified. Say I ...
Read more >Customize an installation of Azure Active Directory Connect
Use custom settings in Azure Active Directory (Azure AD) Connect when you want more options for the installation.
Read more >How many active paths per a LUN on using active/ac...
Solved: Hello everyone, I have a symmetric active/active array controller and two HBAs on the ESXi host(also two SAN switch). In that case,...
Read more >Documentation: 15: 5.9. Schemas - PostgreSQL
A PostgreSQL database cluster contains one or more named databases. Roles and a few other object types are shared across the entire cluster....
Read more >MultipathUsageGuide - Device-mapper and LVM2 Wiki
When multiple paths exists to a storage device(LUN) on a storage subsystem, ... and uses the priority value of the paths to determine...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
i solved this like so:
import {location} from ‘svelte-spa-router’ var path = $location.split(‘/’)[1] //get first part of path … <a href=“#/users” class:active={path == ‘users’ || path == ‘user’}>Users
This is actually not possible today. The closest thing would be to match “/hello*”, but that would match also the case of /helloworld for example.
A proper solution would require supporting regular expressions there.
I’m adding this to the backlog as a feature request and will implement it in the next release.