Skip to content

chore(sdk): add eslint - #827

Merged
markin-io merged 14 commits into
v0.24-devfrom
chore/sdk/add-eslint
Mar 17, 2023
Merged

chore(sdk): add eslint#827
markin-io merged 14 commits into
v0.24-devfrom
chore/sdk/add-eslint

Conversation

@markin-io

@markin-iomarkin-io commented Mar 16, 2023

Copy link
Copy Markdown
Contributor

Issue being fixed or feature implemented

Adds eslint

What was done?

  • Added eslint package for typescript with airbnb config, handled JS files as well
  • Changed certain from errors into warnings in order to not drown in long refactoring which could possibly break some code (check warnRules in .eslintrc.js)
  • Manually fixed eslint errors that do not alter logical constructions (missing vars, long lines, rearranging imports and etc)
  • eslint-ignored errors that require changes in logical constructions and could possibly cause bugs

How Has This Been Tested?

  • CI

Breaking Changes

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated relevant unit/integration/functional/e2e tests
  • I have made corresponding changes to the documentation

For repository code-owners and collaborators only

  • I have assigned this pull request to a milestone

@markin-io
markin-io marked this pull request as draft March 16, 2023 17:33
@markin-iomarkin-io added this to the v0.24.0 milestone Mar 16, 2023
@markin-io
markin-io marked this pull request as ready for review March 16, 2023 17:42
antouhou
antouhou previously approved these changes Mar 17, 2023
@markin-io
markin-io merged commit 2cf7273 into v0.24-devMar 17, 2023
@markin-io
markin-io deleted the chore/sdk/add-eslint branch March 17, 2023 12:25
QuantumExplorer added a commit that referenced this pull request Aug 22, 2026
…is reads
The ranked and having-range executors only rank — every entry was
projected to its (value, key) pair and the resolved primary value
discarded — yet the resolving reads paid up to k primary point reads
per page through the caller's transaction, outside the pinned iterator
view the page came from, so a primary deleted or rewritten by a commit
in between could surface as CorruptedData or pair a newer primary with
an older page. grovedb's keys-only reads (dashpay/grovedb#824,
indexed_*_top_k_paginated_keys / indexed_*_range_keys) return the
ranking pairs straight from the secondary view and never open the
primary; the executors and the e2e test helpers use them.
grovedb pinned to develop head f52adb64, which also carries the
append-only storage accounting (dashpay/grovedb#822 via #825/#826:
write churn reported as replaced bytes, each note's permanent bytes
charged once) and the keys-only projection on the unified PathQuery
(#827). The genesis shielded seeding test passes the grove version to
the commitment tree's save/commit_mmr, which now take it.
The two shielded fee-floor tests (flat fee >= estimated write cost)
remain red at this pin: the estimate for a 1-action transfer is now
~397M credits (storage 133M + processing 264M, the epoch's replaced
bytes at the processing rate) against the 131M flat fee — down from
18.5B at the previous pin, and the subject of the shielded pricing
change that follows this PR.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@markin-io@antouhou