4df5c9a8d5
* exposing coretime wss endpoint to use on relay chain, adjusted hooks to accept api endpoint as a parameter * adjusting hook calls to new parameters * added Tag for coretime types, renamed occupancyType to coretimeType * added cycle progress and cycle end date to summary, fixed the estimation dates * coretime page draft, added hook for gathering all the coretime information in order to show it on relay chain * lint * bumped version * updated coretime chain summary * updated summary, added timeslice for the first sale start, * hook updates to make sure the coretime data is displayed even if workloads are empty, fallback on coreAssignments * removed unused files * lint * tsc * merging parachainIds with renewalIds * if there is no record in potential renewals, then the chain has renewed already * added config for page-coretime * removed hardcoded regionLength value * improved function to find out type * lint * tsc * Fix versioning * fix comments --------- Co-authored-by: tarikgul <tariksnow37@gmail.com> |
||
|---|---|---|
| .. | ||
| src | ||
| package.json | ||
| README.md | ||
| tsconfig.build.json | ||
| tsconfig.spec.json | ||
@polkadot/apps-config
General config for various services, including settings, external links & types. This is a central source of all the configuration settings that can be tweaked. This also means that it can be customized (via PR) to support any additional chains. The internals are split into a number of settings -
- api - Here you can add any chain or node-type specific types configuration. When added, it means that when the UI connects to either a runtime with a spec name, or a chain with a specific name, the types will be automatically added to the API as used in the app.
- endpoints - Configuration for specific per-type chain endpoints.
Customization for each of these are discussed next.
Api
The API config can be done in one of two ways -
- chain - Here we are mapping to a specific chain name. Generally the next type would be preferred, however if you are supporting multiple chains with individual configs, you would probably want to add the chain-specific information in here.
- spec - Here we are mapping from the runtime spec name of the chain to specific types. This means that when connected to a specific spec, these types will be injected.
The actual type definitions you should be familiar with, it is exactly the same as you would upload via the settings page in JSON, or as detailed in the API types pages.
Endpoints
- Add your chain logo (if available) to either
ui/logos/chainsorui/logos/nodes(the second is generally used) - Run the image build command to generate an inline version via
yarn build:images - Add your chain to
endpoints/{production, productionRelay, testing, testingRelay*}as applicable for your deployment - The
ui.colorspecifies the chain color, theui.logo(imported from generated), specifies the specific logo