* chore: update all devDependencies to the latest versions
* chore: update @noble/hashes to 1.3.0
* chore: update @swc/core to 1.3.41
* chore: update @noble/ed25519 by a patch version
* chore: update ts-proto and eslint/parser dev deps
* chore: upgrade pino minor version
* chore: upgrade tsx minor version
* chore: add changeset
* fix: typo in VerificationAddEthAddress
* fix: address and hash types should be Uint8Array not string
* docs: SignerBody is now SignerAddBody or SignerRemoveBody
* docs: clarify MessageData structure
* docs: placeholders for utils
* docs: replace stub data with better defaults
* docs: making verification messages
* poc
* address pr feedback, add pagination to getAllSignerMessagesByFid
* fix types
* use bytes and uint32
* move makeEndPrefix into utils
* getSignersByFid
* fix: getCastsByFid should return items in reverse chronological order
* returns casts in chronological order
* fix: getCastsByFid should return casts in chronological order
In the RocksDB iterator we use to construct thashes for the messages query, select only the CastMessages which are CastAdds
* rename page options and move page iterator to message file
* intermediate commit
* fix tests
* use suffixes as tokens rather than full keys
* remove commented out code
* paginate getCastsByParent, getCastsByMention, getReactionsByCast
* add changeset and fix linting
* update multiPeerSyncEngine test
* add more tests
* fix import
---------
Co-authored-by: bstchow <36556453+bstchow@users.noreply.github.com>
Co-authored-by: Paul Fletcher-Hill <pfletcherhill@gmail.com>
We want to know exactly how many bytes we're storing. Check using utf8
byte length instead of character length.
This also requires changes to our mentions validations, since we now
need to check in terms of bytes instead of characters.
While here, based on team discussion and current cast data, increase
maximum number of mentions from 5 to 10.
* add: SignerAdd and SignerRemove to message.proto
* add: finish message.proto and validations
* progress: refactor signer factory
* update tests to support signerAddBody and signerRemoveBody
* add changeset
---------
Co-authored-by: Paul Fletcher-Hill <pfletcherhill@gmail.com>
* remove: return types on builders.ts
* add: custom return type to makeCastAdd
* add: types to cast add message return
* docs: align left for return table
* update: document the return of functions in builders.ts
* fix: wrong link in returns
* remove: one-liner signatures
* update: add return tables for signers
* add: barebones docs for client.ts
* fix: wrong link in types
* fix: table overflow when function could return two types
* fix: relative path on hubble docs not resolving to contributing.md
* add: initial table structure of the docs
* remove: link on first column
* add: docs/Ed25519Signer.md
* fix: wrong links in Ed25519Signer.md
* fix: wrong link again
* add: constructor to ed25519signer.md
* add docs/Eip712Signer.md
* update: replace ambiguous description with TODO
* update: code example on readme
* add: a comment about neverthrow
* add: js docs to interact with hub
* update: wrong import on docs
* remove: make Data and Amp functions
* update: clarify the eddsa private key part
* update: move signer docs to readme
* update: readme table
* fix: wrong path
* add: docs for eip signer but in js
* remove: ambiguous descriptions
* add: doc generation with TypeDoc
* add: docs for ed25519 signer
* update: build first before running docs
* update: only use packages/js for typedoc entrypoint
* remove: function name in tsdoc comments
* update: move examples up for clarity
* add: typedoc.json
* add: description for properties of signers
* update: link to classes in readme
* update: move make message explanation above
* remove: ambiguous description in readme
* add: a line in contributing.md about generating docs for packages/*
* remove: old docs
* update: recompiled docs and add plugin on typedoc.json
* add: description to sign verification
Co-authored-by: Anthony D'Addeo <tony@tavour.com>
* update: use yarn instead of npm
Co-authored-by: Anthony D'Addeo <tony@tavour.com>
* update: disable typedoc source
* update: contributing.md packages/* to packages/js
* update: TODO to TODO DOCS
* fix: eip712 signer not rendering properly
* add: docs to message builders
* add: docs to client
---------
Co-authored-by: Anthony D'Addeo <tony@tavour.com>
It is possible for a cast to have multiple mentions with the same
position. Consider the following cast:
@a@b@c
In this case, we are mentioning the users `a`, `b`, and `c`, without
separating their names with any other text. The resulting
`mentionsPositions` will be `[0, 0, 0]`, since there is no change in
position.
Relax our validations to allow this case.
