New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Can we reduce the number of concepts for hidden scopes #1276

Open

lukaw3d opened this issue Feb 20, 2024 · 1 comment

Member

lukaw3d commented Feb 20, 2024 •

edited

Loading

ENABLED_LAYERS_FOR_NETWORK
wantedScope (not collapsed in search)
isLayerHidden (not searchable, but is discoverable)
fixedLayer (pinned, single enabled layer) (see discussions in Support limiting scope to one network or layer - full version #1242 and Support limiting scope to one network or layer - simplified version #1269 )
scopeFreedom

(previously also: scope.valid #1159, getEnabledRuntimesForNetwork + getEnabledLayersForNetwork f5f510e )

The text was updated successfully, but these errors were encountered:

Member Author

lukaw3d commented Feb 21, 2024

If we only ENABLE pontus-x on dev/staging, can we remove HIDDEN layers? Differences:

direct links to pontus-x on production won't work https://explorer.oasis.io/testnet/pontusx/block/393840
searching on staging will find pontus-x results

lukaw3d mentioned this issue

Don't run searches against hidden layers #1280

Merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment