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
Could this be enabled to allow a complete config including dye to be
selected from the URL?
I believe that the code that matters for this is in SpekCheck.route_hash. Basically, it looks at the fragment/hash component of the URI. In the case of #setup=foo it looks for a setup named foo and in the case of #setup=foo#dye=bar, it will look for a setup named foo#dye=bar. It's typical to split the fragment component with & so that's a solution.
However, to note that a setup includes a dye (although in most cases we have it empty) so it's a bit weird to specify both a setup and dye. I guess that we could have it so that #setup=4pi&dye=gfp will apply gfp on top of the 4pi setup and dye=gfp&setup=4pi will apply the 4 pi setup on top of the gfp dye (possibly setting the dye to something else).
The text was updated successfully, but these errors were encountered:
Requested by @iandobbie:
I believe that the code that matters for this is in
SpekCheck.route_hash
. Basically, it looks at the fragment/hash component of the URI. In the case of#setup=foo
it looks for a setup namedfoo
and in the case of#setup=foo#dye=bar
, it will look for a setup namedfoo#dye=bar
. It's typical to split the fragment component with&
so that's a solution.However, to note that a setup includes a dye (although in most cases we have it empty) so it's a bit weird to specify both a setup and dye. I guess that we could have it so that
#setup=4pi&dye=gfp
will apply gfp on top of the 4pi setup anddye=gfp&setup=4pi
will apply the 4 pi setup on top of the gfp dye (possibly setting the dye to something else).The text was updated successfully, but these errors were encountered: