Refactor pallet_identity
-
AccountLinkeroptimization -
Remove unused BenchmarkSetupHandler -
Fix clippy errors with runtime-benchmarks feature on -
Enforce clippy for benchmarks -
close #103 (closed)
Merge request reports
Activity
changed milestone to %runtime-800
added RN-runtime label
assigned to @bgallois
- Resolved by Benjamin Gallois
I've incorporated metadata generation at the commit level, but it's a bit cumbersome as it necessitates compiling and starting a node before generating the metadata. This process can be bypassed using
git commit --no-verifyfor trivial commits.Moving the metadata server-side to the CI pipeline doesn't seem like a viable solution either. It would require adding a commit after each change to avoid metadata errors during testing, or it could be done at merge. In the latter solution, developers would still need to manually update metadata when tests fail.
If the current approach is too cumbersome, one possible solution is to keep the metadata generation helper script and the Cargo dependency. Simultaneously, we can add a section in the documentation explaining the metadata process, including when and how to regenerate them if needed.
- Last reply by Hugo Trentesaux
requested review from @HugoTrentesaux
added 2 commits
