Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

CUSTOM_TYPES from `src/config/common.json` are ignored

See original GitHub issue

After adding a new type to my pallet and changing common.json to look like:

{
  "APP_NAME": "substrate-front-end-tutorial",
  "DEVELOPMENT_KEYRING": true,
  "RPC": {},
  "CUSTOM_TYPES": {
    "SomeTypeX": "u64"
  }
}

I get Cannot construct unknown type SomeTypeX. If I place it in src/config/development.json instead, the frontend loads just fine.

(I use yarn start for a dev environment) Is this expected behaviour? I would have thought that common.json serves all environments.

Thanks!

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:6 (5 by maintainers)

Top GitHub Comments

1reaction

mmagiciancommented, Sep 21, 2020

Thanks for taking the time to check it. I modified the node template though, I’ll try to publish my fork later so you can see what I was doing exactly.

0reactions

wheresaddiecommented, Sep 24, 2020

closing issue due to inactivity, if issue continues, please follow up with new issue @mmagician

Top Results From Across the Web

integritee-network/crowdloan - GitHub

When writing and deploying your own front end, you should configure: Custom types as JSON in src/config/types.json . See Extending types. PROVIDER_SOCKET in ......