add tests, refactor a bit
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Sep 16 2024
let's add some tests
add missing headers
Sep 14 2024
This has a weird double-scroll behavior. Isn't just simpler to just put all the stuff in cashtab and let the browser handle the scrolling?
Sep 13 2024
Sep 12 2024
Sep 11 2024
Sep 10 2024
@bot ecash-agora-tests
add test to build, fix test
improve comments, use 32 for bits, address other nits
Sep 9 2024
Sep 5 2024
rebase on D16723
separate out fix
Sep 2 2024
Aug 30 2024
Aug 28 2024
Works for me 👍🏻
Aug 27 2024
rebase on master
Aug 26 2024
In D16544#378081, @bytesofman wrote:Not sure what you’re asking there
In D16544#378062, @bytesofman wrote:update using a dataclass
could you summarize what this does and why this became preferable? I can see the organization change, is it just easier to read and maintain as a class?
Aug 22 2024
rebase to fix build
fix hopefully the last test
fix other tests
fix groups for the error case
move agora.py into ecash-agora (so it becomes part of the npm package), rebase to fix tests, update + fix comments
fix tests in context.rs
minor fixes/cleanup, rebase on D16674
remove unrelated chronik-db change
rebase, update using a dataclass, add sats calculation as requested
fix comments
Aug 21 2024
Aug 20 2024
fix missing =
fix lint length
use djlint to lint explorer templates
Aug 19 2024
Aug 16 2024
Aug 15 2024
Another possible name would be gettransactionstatus; you already say this in the release notes: "retrieve the status of a non-mined transaction". It would (kinda) imply that the RPC should return "mined" for mined txs (which we can't do in the general case because the -txindex can be disabled). So either it looks that up (and returns "unknown" if the txindex is off), or the name could also be gettransactionstatusinmemory, which is I think the most precise, albeit a bit long.