You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
is there a possibility to
extend this to the login page? In my case, I have a script that dumps the
status of multiple environments, I'd like it to be the first thing people
see if they log in
The text was updated successfully, but these errors were encountered:
@MNeill73 should they see this info only when they login? Or any time they start a new session? Login is performed every X days (30 by default), so showing such info every 30 days doesn't make much sense to me.
Also, if a user opens specific script URL (from a bookmark, for example), e.g. http://localhost:5000/index.html#/Very%20parameterized should he still see this global preload script? Or only when he opens http://localhost:5000/index.html ?
I envision them seeing it on the "home" screen any time they land on it,
the big empty canvas where there's nothing until you select a script.
If they go directly to a script URL, then no, they wouldn't see this, they
should see whatever that script has configured for its own preload
On Thu, Mar 16, 2023 at 5:12 AM Iaroslav Shepilov ***@***.***> wrote:
@MNeill73 <https://github.com/MNeill73> should they see this info only
when they login? Or any time they start a new session? Login is performed
every X days (30 by default), so showing such info every 30 days doesn't
make much sense to me.
Also, if a user opens specific script URL (from a bookmark, for example),
e.g. http://localhost:5000/index.html#/Very%20parameterized should he
still see this global preload script? Or only when he opens
http://localhost:5000/index.html ?
—
Reply to this email directly, view it on GitHub
<#639 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3HBI3R24VZJAFEBOPYQ233W4LKOZANCNFSM6AAAAAAV45MNAA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
From #218 (comment)
@MNeill73:
The text was updated successfully, but these errors were encountered: