We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Presently you have to duplicate where you want to load from and to for the inline feature:
<a data-trimmings-inline="from: main, to: main" href="/cake" > Cake </a> ... etc ... etc
This can get pretty repetitive if you serve just a partial from the server of the exact element to be replaced.
So it would be great if the from and to were both optional and infered based on the top-root element in response from the server.
from
to
For example:
<a data-trimmings-inline href="/cake" > Cake </a>
Response from server:
<main>.....</main>
Trimmings will assume from: main, to: main
from: main, to: main
Another example:
<a data-trimmings-inline="to: custom-main" href="/cake" > Cake </a>
Assuming the same response from the server <main> trimmings will essentially assume:
<main>
from: main, to: custom-main
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Presently you have to duplicate where you want to load from and to for the inline feature:
This can get pretty repetitive if you serve just a partial from the server of the exact element to be replaced.
So it would be great if the
from
andto
were both optional and infered based on the top-root element in response from the server.For example:
Response from server:
Trimmings will assume
from: main, to: main
Another example:
Assuming the same response from the server
<main>
trimmings will essentially assume:from: main, to: custom-main
The text was updated successfully, but these errors were encountered: