Skip to content
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

More configuration options for paratimes #1441

Merged
merged 10 commits into from
Aug 13, 2024
Merged

More configuration options for paratimes #1441

merged 10 commits into from
Aug 13, 2024

Commits on Aug 13, 2024

  1. Add support for overriding names of special scopes 

    Normally, the name of a scope is derived by concatenating
the name of the layer (i.e. "Sapphire") and
the name of the network (i.e. "Testnet") ==> "Sapphire Testnet"

However, in some specific cases, we might want to have something different.
This can be achieved by this override function.
    @csillag
    csillag committed Aug 13, 2024
    Configuration menu
    Copy the full SHA
    1c0439c View commit details
    Browse the repository at this point in the history

  2. Centralize how scope routes are built

    @csillag
    csillag committed Aug 13, 2024
    Configuration menu
    Copy the full SHA
    16f838c View commit details
    Browse the repository at this point in the history

  3. Add code for customizing scope paths 

    Normally the "sapphire" paratime on the "testnet" network will be
available via "testnet/sapphire".

This commit adds a config option to override the paths for
specific paratimes with any two-word constant.

(So that we can use "magic/kingdom" instead of "testnet/sapphire",
if we want to.)
    @csillag
    csillag committed Aug 13, 2024
    Configuration menu
    Copy the full SHA
    1ace609 View commit details
    Browse the repository at this point in the history

  4. Add config variable for skipping the graph 

    This is mostly useful if we want to restrict a deployment
to display only a few layers.
    @csillag
    csillag committed Aug 13, 2024
    Configuration menu
    Copy the full SHA
    287db7b View commit details
    Browse the repository at this point in the history

  5. Rename ThemeByNetwork to ThemeByScope, preparing for extension

    @csillag
    csillag committed Aug 13, 2024
    Configuration menu
    Copy the full SHA
    fdb3e58 View commit details
    Browse the repository at this point in the history

  6. Rename NetworkSpecificPart to ScopeSpecificPart, preparing for extension

    @csillag
    csillag committed Aug 13, 2024
    Configuration menu
    Copy the full SHA
    2e97ccb View commit details
    Browse the repository at this point in the history

  7. Change semantics of getThemesForNetworks function 

    Up to now, this function has returned all the themes, for all networks.
Now it will only return one theme, for the requested network.
    @csillag
    csillag committed Aug 13, 2024
    Configuration menu
    Copy the full SHA
    12ef675 View commit details
    Browse the repository at this point in the history

  8. Rename getThemeForNetwork to getThemeForScope, preparing for extension

    @csillag
    csillag committed Aug 13, 2024
    Configuration menu
    Copy the full SHA
    19e662a View commit details
    Browse the repository at this point in the history

  9. Extend getThemeForScope function to accept layer

    @csillag
    csillag committed Aug 13, 2024
    Configuration menu
    Copy the full SHA
    e32b1ad View commit details
    Browse the repository at this point in the history

  10. Add support for adding custom themes for specific paratimes

    @csillag
    csillag committed Aug 13, 2024
    Configuration menu
    Copy the full SHA
    04a6871 View commit details
    Browse the repository at this point in the history