webbdays/pocket

AddrBook management optimization and refactoring** [#246](github.com/pokt-network/pocket/issues/246)

todo 🗒️

#283

· github-actions opened

on Jan 12, 2023

Consider create a type for signature and having constraints for each type as well.

todo 🗒️

#282

· github-actions opened

on Jan 12, 2023

This could (should?) be a codebase-wide shared test helper

todo 🗒️

#281

· github-actions opened

on Jan 12, 2023

research `badger.views` for further improvements and optimizations

todo 🗒️

#280

· github-actions opened

on Jan 12, 2023

This is only used in tests. Should we remove it?

todo 🗒️

#279

· github-actions opened

on Jan 12, 2023

Consider renaming `highPrepareQC` to simply `prepareQC`

todo 🗒️

#278

· github-actions opened

on Jan 12, 2023

marked for removal since we'll implement a better pattern for dependency injection

todo 🗒️

#277

· github-actions opened

on Jan 12, 2023

Not part of `TestMain` because a mock requires `testing.T` to be initialized.

todo 🗒️

#276

· github-actions opened

on Jan 12, 2023

define UX for return values - should we return the raw response or a parsed/human readable response? For now, I am simply printing to stdout

todo 🗒️

#275

· github-actions opened

on Jan 12, 2023

Dmitry has expressed multiple times that this should be a gauge instead of a counter

todo 🗒️

#274

· github-actions opened

on Jan 12, 2023

this is a temporary solution that guarantees backward compatibility while we implement peer discovery.

todo 🗒️

#273

· github-actions opened

on Jan 12, 2023

Consider removing all `Set` methods (e.g. `SetAccountAmount`) and replace with `Add` (e.g. `AddAccountAmount`) by having it leverage a "default zero".

todo 🗒️

#272

· github-actions opened

on Jan 12, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

AddrBook management optimization and refactoring** [#246](github.com/pokt-network/pocket/issues/246)

Consider create a type for signature and having constraints for each type as well.

This could (should?) be a codebase-wide shared test helper

research `badger.views` for further improvements and optimizations

This is only used in tests. Should we remove it?

Consider renaming `highPrepareQC` to simply `prepareQC`

marked for removal since we'll implement a better pattern for dependency injection

Not part of `TestMain` because a mock requires `testing.T` to be initialized.

define UX for return values - should we return the raw response or a parsed/human readable response? For now, I am simply printing to stdout

Dmitry has expressed multiple times that this should be a gauge instead of a counter

this is a temporary solution that guarantees backward compatibility while we implement peer discovery.

Consider removing all `Set` methods (e.g. `SetAccountAmount`) and replace with `Add` (e.g. `AddAccountAmount`) by having it leverage a "default zero".

Issues

Search results