Unanimous agreement amongst the team for updating the GitHub repositories to all use the - separator, so that’s now been done.
Not quite as simple to update the crate names on crates.io or in each repo’s Cargo.toml unfortunately, but hopefully that doesn’t cause too much confusion.
@tfa I’ve raised a PR to your repo with the updates to the new repo names in the generate.sh script, but self-encryoption won’t link up wonder if you could take a look whenever you get the chance?
Note that I’ve got to go offline for a few hours, be back online later
It’s just that in safe-client-libs Cargo.toml files this dependency is still spelled self_encryption. See in safe_app and safe_core. This must be corrected at first.
That was my first thought, but then I’ve not updated the Cargo.toml files of any repos & all the other connections still worked…but now looking back at the graph with fresh eyes tonight I see that the difference is that all the others I’ve renamed don’t have direct incoming arrows, or are hardcoded a-la safe-app-csharp.
Ok great, the safe_app & safe_core cargo.tomls won’t be updated until Lionel gives that the go ahead tomorrow no doubt, so the graph will look broken after tonight’s scheduled run, but will be back to normal after we’ve updated that. Thanks!
@ravinderjangra, I am not sure about sn_authenticator_mobile dependency on sn_client. I did this because previously safe-authenticator-mobile was dependent on safe_authenticator_ffi of safe_client_libs which was renamed to sn_client and is mono crate now.
Edit: I think that line <PackageReference Include="MaidSafe.SafeApp" Version="0.5.0-rc2" /> in csproj file means that sn_authenticator_mobile depends on sn_csharp. I have updated SLD accordingly.