0xLugon
0xLugon
> There seem to be a lot of merge conflicts, which are probably our fault because the runes part of the codebase is changing a lot. Could you fix them?...
@raphjaph hope you spend time to review this PR!
all tests is ok
> `RUNE_ID_TO_RUNE_NUMBER` is, as far as I can tell, not needed. To get rune `N`, you can open `RUNE_ID_TO_RUNE_ENTRY`, and use `.skip(N)` to get to that rune, since rune IDs...
@casey @raphjaph what do you think about it?
`define_table! { NUMBER_TO_RUNE, u64, u128 }`
```rust define_table! { NUMBER_TO_RUNE_INFO, u64, RuneInfoValue } #[derive(Debug, PartialEq, Copy, Clone, Serialize, Deserialize)] pub struct RuneInfo { pub id: RuneId, pub entry: RuneEntry, } pub(super) type RuneInfoValue = ( RuneIdValue,...
I need the feedback. @casey @raphjaph If this idea is not necessary, please give me comments. Thankssss
I try to use `RUNE_ID_TO_RUNE_ENTRY` to query but I dont know how to limit and chunk to pagination. Please review this issue.
@raphjaph merge latest and fix conflict