The parameter I am talking about specifically is the __generatorLastEditTime parameter.

This is a visual example:

The URL: https://perchance.org/vue-router?__generatorLastEditTime=1752040569107#/

Is there any problem in removing it?

I was using Vue Router with its createWebHashHistory() API to make hash routes for an application, since Perchance doesn’t support actual routes for apps.

I made a simple logic to simply remove it.

const url = new URL(location.href)
url.searchParams.delete('__generatorLastEditTime')
history.replaceState(null, '', url)

Now you get a cleaner URL instead.

The URL: https://perchance.org/vue-router#/about

You can check out the project here.

  • Coc̀éll@lemmy.worldOPEnglish
    1·
    11 months ago

    So, I decided to to look into Perchance’s internal code myself, since I couldn’t get an answer.

    A screenshot that shows Perchance's internal scripts using the parameter and parameter along with some other logic.

    And it looks like Both the __generatorLastEditTime parameter and the __initWithDataFromParentWindow parameter are needed ONLY during the initial load.

    And looking at this part of the code, it seems like Perchance dev is already moving away from the __generatorLastEditTime parameter.

    // if(window.location.href.includes("__generatorLastEditTime=")) return;

    So, I am assuming it is fine to remove these two parameters after the app has loaded. However, I could be wrong, these are just my general understanding after looking into the internal logic.