feat: optimize get fragment visit

[hirasso]

Description

I just stumbled upon a case where the sole fragment that was being targeted for the current visit already had the same fragment url as visit.to.url, causing a normal (non-fragment) visit that broke as of course the containers were missing (hard to explain 😅). ~Allowing visits that don't replace anything was exactly what I needed in this case~.

Actually, the comment I posted below lead me to the real solution: Treat a visit as a reload, if all fragment elements already match that visit's visit.to.url. In other words: Don't skip fragments as described in https://swup.js.org/plugins/fragment-plugin/#how-fragment-containers-are-found, bullet 3, if otherwise no fragments would be replaced at all.

• includes Version bump and changelog update

Drive-By

• The visit introduced for rule.if had the wrong route if being called as an API function. It will now be created on the fly using swup.createVisit(route).

Checks

• [x] The PR is submitted to the master branch
• [x] The code was linted before pushing (npm run lint)
• [x] All tests are passing (npm run test)
• [x] New or updated tests are included
• ~The documentation was updated as required~

Additional information

[github-actions[bot]]

Playwright test results

 12 passed

Details

 12 tests across 1 suite
 
 6b6d10d

[hirasso]

An alternative could be to check if all containers for the current visit already match the visit.to.url, and if so, replace them anyways. @daun Maybe this is something we should discuss in a call.

[hirasso]

Closing this as I'd like to go through all this in an issue first.