How should Ğ1 lib expose v2 features?

In a recent discussion we suggested multiple options for Ğ1 lib to expose both v1 and v2 features:

  • have two git branches “v1” and “v2”
  • use a different namespace
  • use shared namespace and hide the transition under the hood so that apps developed on v1 still work on v2

Also, Ğ1 lib will expose polkadotjs API as well as duniter-specific wrapped versions. How could the user load only the parts he needs to keep dependency as light as possible?

@1000i100 can you explain your point of view?

1 Like