jmoiron/sqlx 9128
general purpose extensions to golang's database/sql
niftyswap - decentralized swap protocol for ERC-1155 tokens
Go-Ethereum dev toolkit
Arcadeum Smart Wallet
pkieltyka/amqp-flash-ruby-rpc 10
A demonstration of Flash and Ruby interoperating over AMQP
ETHAuth -- self-signed authorization proofs
ETHAuth -- self-signed authorization proofs
horizon-games/SkyWeaver-desktop 8
SkyWeaver desktop app -- via Electron
This is an implementation of the 0-8 version of AMQP for AS3.
push eventwebrpc/webrpc
commit sha 21e29fe43bb1d0bb3f47a1d8070e1978de1ac0ae
migrate from TSLint to ESLint (#82) TSLint has been the recommended linter in the past but now TSLint is deprecated and ESLint is taking over its duties. from https://code.visualstudio.com/api/advanced-topics/tslint-eslint-migration
push time in 11 hours
PR merged webrpc/webrpc
TSLint has been the recommended linter in the past but now TSLint is deprecated and ESLint is taking over its duties.
from https://code.visualstudio.com/api/advanced-topics/tslint-eslint-migration
pr closed time in 11 hours
issue commentwebrpc/webrpc
examples: add auth+acl example like we do in some of our apis
@ottob that certainly works, but also since the generated api accepts a fetch method as an argument, you can actually wrap it and add additional functionality, such as automatically setting the jwt. See for instance the example below which is some code I've pulled out from one of my projects
export * from './api.gen'
import { ArcadeumAPI as BaseArcadeumAPI } from './api.gen'
export class ArcadeumAPI extends BaseArcadeumAPI {
jwtAuth: string | undefined = undefined
constructor(hostname: string) {
super(hostname, window.fetch)
this.fetch = this._fetch
}
_fetch = (input: RequestInfo, init?: RequestInit): Promise<Response> => {
return new Promise<Response>((resolve, reject) => {
// automatically include jwt auth header to requests
// if its been set on the api client
const headers = {}
if (this.jwtAuth && this.jwtAuth.length > 0) {
headers['Authorization'] = `BEARER ${this.jwtAuth}`
}
// before the request is made
init!.headers = { ...init!.headers, ...headers }
window.fetch(input, init).then(resp => {
// after the request has been made..
resolve(resp)
}).catch(err => {
// request error
reject(err)
})
})
}
}
comment created time in 11 hours
issue commentethers-io/ethers.js
Add EIP-712 Ancillary Package for v5.
Neat, thats a cool way to introduce experimental/new features to prod dists
comment created time in a day
issue commentethers-io/ethers.js
Add EIP-712 Ancillary Package for v5.
@ricmoo exciting to have this directly inside of ethers v5. How come the signTypedData method is underscored in the prefix? ie. https://github.com/ethers-io/ethers.js/blob/master/packages/tests/src.ts/test-utils.ts#L773 as well https://github.com/ethers-io/ethers.js/blob/master/packages/tests/src.ts/test-utils.ts#L759
comment created time in a day
startedsafebash/opencrypto
started time in 5 days
startedc-smile/sciter-js-sdk
started time in 6 days
issue commentgo-chi/jwtauth
Move away from unmaintained dgrijalva/jwt-go
Free OSS is more like a potluck, and less of a restaurant
comment created time in 7 days
issue commentgo-chi/jwtauth
Move away from unmaintained dgrijalva/jwt-go
Submit a PR then
comment created time in 7 days
push eventpkieltyka/qmk_firmware
commit sha e8bdb9a94fe079b1d4a7455128441c067d305bdd
cc_ctl improvement
push time in 7 days
push eventpkieltyka/qmk_firmware
commit sha 85f7801446053aa5143ab3a328b9c96fb0a44f1f
left control as special key
push time in 7 days
push eventpkieltyka/qmk_firmware
commit sha 5246acb2e4c188198d503856a493b66174486db8
[Keyboard] Add support for Ace of Spades TKL keyboard (#9128) * Add support for Ace of Spades * Fix the F-row mappings * Add the tkl_iso layout * Put KC_PAUS back in place of top layer reset * aholland909 personal keymap for Ace of Spades * Address PR feedback and rename to aos/tkl * Rename keyboard implementation filenames * Remove unnecessary layers * info.json for the configurator
commit sha 179e5c018fcee9bcb0a7f1907cc96d44ed5cf554
CLI: Rework submodule checking (#9162)
commit sha 6d84795bc1e4b867725e3ddd906af9e125f71e3b
Update ARM split keyboard docs (#9160) * Update ARM split keyboard docs * Update docs/serial_driver.md Co-authored-by: Nick Brassel <[email protected]> Co-authored-by: Nick Brassel <[email protected]>
commit sha fd4f1029771fba4d620ca6cfc9710ccbba421206
Fix build. (#9163)
commit sha 9e4037465afe5a6e1888d4bf2a0b80fee9beed99
[Keyboard] Wolfmark Club WM1 (#9121) * do the basic port for the WM1 * with much help from tzarc, get the addresses correct * make the keymap more closely mirror what the board has * Add QMK Configurator support * update the readme * get indicator leds working * enable RGB underglow * fix up rgb underglow * add notes regarding existence of backlight * Update keyboards/wolfmarkclub/wm1/readme.md * Update keyboards/wolfmarkclub/wm1/rules.mk * Update keyboards/wolfmarkclub/wm1/rules.mk * Update keyboards/wolfmarkclub/wm1/rules.mk * Update keyboards/wolfmarkclub/wm1/rules.mk * Update keyboards/wolfmarkclub/wm1/config.h * Update keyboards/wolfmarkclub/wm1/ld/wm1_f103.ld * Update keyboards/wolfmarkclub/wm1/bootloader_defs.h * Update keyboards/wolfmarkclub/wm1/config.h * Update keyboards/wolfmarkclub/wm1/rules.mk * Update keyboards/wolfmarkclub/wm1/wm1.c * Update keyboards/wolfmarkclub/wm1/wm1.c * Update keyboards/wolfmarkclub/wm1/rules.mk * Update keyboards/wolfmarkclub/wm1/rules.mk * Update keyboards/wolfmarkclub/wm1/readme.md * Update keyboards/wolfmarkclub/wm1/rules.mk * Update keyboards/wolfmarkclub/wm1/rules.mk * Update keyboards/wolfmarkclub/wm1/rules.mk * Update keyboards/wolfmarkclub/wm1/rules.mk * update readme
commit sha 7ef2ea3d492f07a069b0dbbb2459d6b8149ddf29
Improve the Makefile message a bit more (#9161)
commit sha 53224e03d62a4d0bd7c9f7e63fd6222ec649a4fa
[Keyboard] handwired/k8split (#9133) * New Keyboard: k8split * Apply suggestions from code review * move NKRO rule to keymap scope
commit sha 38d2c8cedf9f9f43b5ba372ffd38ccc7cc96be15
[Keymap] dohmain 60_tsangan_hhkb layout (#9157) * initial commit for tsangan_hhkb community layout * keymap.c done * wrote readme * move media keys; add shortcuts * edit to reflect changes in keymap * update readme with imgur link
commit sha 503cf18aedc8166bb5a84e15fb0c6c6da6d47f53
ymdk/bface - RGB config and minila layout (#9127) * Fix info about RGB LEDs on the bottom. * Added RGB LEDs support * Added RGB LEDs config options * Added minila layout with RGB keys * Create readme.md * Update keyboards/ymdk/bface/keymaps/minila/keymap.c Co-authored-by: Joel Challis <[email protected]> * Update keyboards/ymdk/bface/keymaps/minila/keymap.c Co-authored-by: Joel Challis <[email protected]> * Update keyboards/ymdk/bface/keymaps/minila/keymap.c Co-authored-by: Joel Challis <[email protected]> * Update keyboards/ymdk/bface/keymaps/minila/readme.md Co-authored-by: James Young <[email protected]> * Update keyboards/ymdk/bface/keymaps/minila/readme.md Co-authored-by: James Young <[email protected]> Co-authored-by: Joel Challis <[email protected]> Co-authored-by: James Young <[email protected]>
commit sha f66680d233d1abf61a38d3704a99941c62bfebbc
Fixed the indentation of the sample code in feature_pointing_device docs (#9177) * Fixed the indentation of the sample code in docs/feature_pointing_device.md sample. * Update docs/feature_pointing_device.md Co-authored-by: Joel Challis <[email protected]> Co-authored-by: Joel Challis <[email protected]>
commit sha 2ac3a51d71a05fe46fc6967797b0d34d8fb3fcd8
Fix SPI EEPROM compile issue when Console is enabled (#9193)
commit sha 883dd2df80edf084d100c61c1b61782bfa5503f9
Fix i2c EEPROM compile issue when Console is enabled (#9186) * Fix i2c EEPROM compile issue when Console is enabled * Only use if both console and debugging is enabled
commit sha dc6fe85b87a62ddba13b501a8d81bea9d5ff563b
[Keyboard] Add zvecr/split_blackpill (#9166) * Add split_blackpill keyboard * Add RGB config * tidy up rules * fix usage of layer_state_t * Apply suggestions from code review * Apply suggestions from code review * Apply suggestions from code review * Add configurator support
commit sha 6ca00c2152831885e719a31e606bf041601a7a16
[Keyboard] PDBDOWN should be PCBDOWN. (#9192)
commit sha d8f76f9e6dd76b20636f7726f98aac9c26d03aa5
Added missing shutdown_user() hook (#9180) * add missing shutdown_user() * use reset_keyboard() from quantum
commit sha f56d333db1a2dc4ec20de410ec9a26e5195e4411
[Keyboard] Added wilba.tech WT60-XT (#9168) * Added wilba.tech WT60-XT * fix indent * Update keyboards/wilba_tech/wt60_xt/readme.md * Update keyboards/wilba_tech/wt60_xt/rules.mk * Update keyboards/wilba_tech/wt60_xt/wt60_xt.c
commit sha 5c9906eb4fc569cd08d88dcd85ce9afaa5410ffb
Add VIA support for kbd67rev1 (#9173)
commit sha e4823aadec24bca0ecfd1184562d27a49fd20544
Fix capitalisation of "GitHub" (#9184)
commit sha ba5e1f1bae1d724ab9b08229c2ce89d8d7714706
[Keymap] update helix/rev2:yshrsmz keymap (#9047) * update helix keymap * use set_single_persistent_default_layer
commit sha 9d41281a1d09c8bd3ae1c0a8bd6df95ada899451
[Keyboard] Add Key 65 by Fox Lab (#9116) * Add Key65 Universal PCB * Add ISO layout to universal * Correct universal info.json * Add Key 65 Hotswap * Correct typo in Key 65 Universal * Update readmes * Correct name * Update keyboards/foxlab/key65/hotswap/config.h * Apply suggestions from code review * Invert capslock LED state * Avoid initial capslock LED flash * Apply suggestions from code review * Update rules.mk * Apply suggestions from code review
push time in 7 days
startedOffchainLabs/arbitrum
started time in 7 days
push eventarcadeum/arcadeum.js
commit sha d145a4366309ebdcf5d7b12dadc90fb7167853b0
focus wallet upon receiving request from dapp
push time in 8 days
push eventgo-chi/chi
commit sha 2e5656d201cedacc8732005b7846d9cb21a48579
Make README godoc link more useful (#546) I was initially confused by difference between what I was seeing in the documentation versus using Chi, until I realized I was looking at 4 year old docs. As far as I can tell, there isn't a perfect solution here. The pragmatic solution seems to be to ask the reader to pick the version they want to see.
push time in 11 days
PR merged go-chi/chi
I was initially confused by difference between what I was seeing in the documentation versus using Chi, until I realized I was looking at 4 year old docs. Sadly, the new pkg.go.dev server doesn't make it easy to see the correct version.
As far as I can tell, there isn't a perfect solution here. The pragmatic solution seems to be to ask the reader to pick the version they want to see.
pr closed time in 11 days
issue commentgo-chi/chi
Reliance on io.ReaderFrom from unexposed `response` in net/http
hey all, if someone can produce a breaking test case to demonstrate the problem (with stdlib), then I'll include it in the middleware tests and find a solution
comment created time in 12 days
PR closed go-chi/chi
Pull requests for adding chi compatible middleware to the list are just rejected, in opposition to what the README says.
This pull request updates the documentation to reflect this, ref pull request #537.
pr closed time in 13 days
pull request commentgo-chi/chi
Update the documentation, ref PR #537
https://github.com/go-chi/chi/commit/c4e3a750be5a34333b454df69dd81f2ff38f7d91
comment created time in 13 days
push eventgo-chi/chi
commit sha c4e3a750be5a34333b454df69dd81f2ff38f7d91
README
push time in 13 days
startedcrytic/slither
started time in 13 days
issue commentgo-chi/chi
Reliance on io.ReaderFrom from unexposed `response` in net/http
this is a tricky one as it may have whack-a-mole implication with other libraries. I'd have to dive back into the problem space in order to give proper advice and I'm not available for that at the moment
comment created time in 15 days
issue commentgo-chi/chi
Reliance on io.ReaderFrom from unexposed `response` in net/http
PR's are welcome, but please provide lots of tests
comment created time in 16 days
issue commentgo-chi/chi
RealIP allows any value, including non-IP addresses and private IP addresses
this isn't really a bug with chi as it relies on the headers from the upstream -- we can only assume each upstream is forwarding the correct ip address of its sender. The other issue is that upstream's sometimes have this in the opposite order, so it's a bit inconsistent. If anyone can point me on some definitive text on the best way to get the real IP from a proxied request, as in which ordering is the most correct, we'll stick to that.
comment created time in 17 days
PR closed go-chi/chi
Add a link to permissions2, a package that has a Midddleware function that is written specifically for chi.
pr closed time in 17 days
pull request commentgo-chi/chi
thanks for the PR but I prefer to keep the list down to just go-chi packages
comment created time in 17 days
PR closed go-chi/chi
What I do?
- Add one more request logger to only log request for http status 4xx/5xx response
Logger4xxAnd5xx
Reason why I do this
Currently middleware Logger will log every request whether it's 2xx, 3xx, 4xx, and 5xx. Sometimes we only need to log for unsuccessful request. That's why I propose this middleware.
In my project, logs are filled by http 200 request which most of them are health check (I run my project on kubernetes, so I need to provide health check endpoint). It's so painful to see my log full of unnecessary log like this. It makes me hard to find/see if error happened.
pr closed time in 17 days
pull request commentgo-chi/chi
Add request logger only for 4xx and 5xx
thanks for the PR, but I think this logger belongs in a subpackage on your repo, and not part of the chi core. If you're getting a lot of noise from healthchecks, write a middleware which skips those from the logger.
The one PR I would potentially accept is one that passes a filter func from a request and then you can skip the logger, at which point you could skip non 4xx/5xx, or skip the health checks
comment created time in 17 days
issue commentgo-chi/chi
Reliance on io.ReaderFrom from unexposed `response` in net/http
sounds like a bug with apmhttp? alternatively, dont use the logger chi/middleware which causes this to appear
comment created time in 17 days
startedhypha-network/hypha-desktop
started time in 18 days
created tagarcadeum/arcadeum.js
Javascript & Typescript client for Arcadeum Transaction Relayer, available for Browsers and Node
created time in 21 days
push eventarcadeum/arcadeum.js
commit sha 085147a2e17d85219cfcf1228c992b939ef1a2bb
Release v0.4.0
push time in 21 days
delete branch arcadeum/arcadeum.js
delete branch : preserve-chaind-pending-message
delete time in 21 days
push eventarcadeum/arcadeum.js
commit sha 88afef7cc5fb158079e32ba6d6e971cb8272c12b
Preserve chaind pending message (#49) * Create 0.3.42 version * Preserve chainId on pending message
push time in 21 days
PR merged arcadeum/arcadeum.js
pr closed time in 21 days
push eventarcadeum/arcadeum.js
commit sha 629c019732bec3968310aee52a4bc1517125fdc6
ExternalWalletProvider, handling dialog close
push time in 21 days
push eventarcadeum/arcadeum.js
commit sha 75f6ea3d2123669397d2ba11e379cc74dbc952a8
provider: add getAuthSigner() to WalletProvider
push time in 21 days
issue commentBeTomorrow/micro-observables
also, a bit off topic.. but as an FYI we tried to port micro-observables to mobx6 to see how they feel and its quite similar of an interface which is cool: https://github.com/horizon-games/cacheness/commit/6a5d3a795b18ea72a860f1ffbd3280a3cebb9408
I still prefer micro-observables, but thought you might be interested in this experiment / comparison
comment created time in 22 days
issue openedBeTomorrow/micro-observables
I think it'd be great to have a middleware adapter interface for getters/setters and maybe other stuff. It would be useful to attach things like a logger during debugging situations to find out the code path of code being set. I feel it would be pretty easy to add too
btw (as an aside point), mobx6 came out today and its certainly cleaner then mobx4/5, but I still feel the micro footprint of micro-observables and smaller surface api makes for a better experience. However mobx is definitely more battle tested and has things like middleware for logging. My main thing with micro-observables is ensuring im not re-rendering more often than I want, and also to ensure consistency of the data as its being updated, perhaps this is why mobx encourages to make updates within an action() call. Maybe micro-observables should also have some explicit call to make a batch'd update in a single tick instead of having multiple state updates go across render ticks and make for unnecessary re-renders.
another interesting fact.. micro-observables/src/* is 328 lines of code, and mobx/src/* is 5312 lines of code.. 93% smaller which is a pretty awesome achievement, but I still think more can be done to micro-observables to make it better while still keeping the surface api as small as possible and keeping spirit of explicitness
created time in 22 days
startedbenawad/destiny
started time in 22 days
startedstreamich/react-use
started time in 22 days
startedtannerlinsley/react-query
started time in 23 days
startedreach/reach-ui
started time in 23 days
push eventarcadeum/ethgas-app
commit sha 2ad7a41029c95170f81424cacea0f00d528f1b3e
fix
push time in 24 days
created tagarcadeum/arcadeum.js
Javascript & Typescript client for Arcadeum Transaction Relayer, available for Browsers and Node
created time in 24 days
push eventarcadeum/arcadeum.js
commit sha 472008a17f19041687a60c43a771a577db751ca3
Release v0.3.4
push time in 24 days
push eventarcadeum/arcadeum.js
commit sha ef133e2125120274c468b4dd406ed2c6d9e7a58e
authChain sign methods (#46) * Add authChain methods * Accept chainId number on signMessage * Fix return type isMultiWallet
push time in 24 days
PR merged arcadeum/arcadeum.js
- Add
signAuthMessagemethod to MultiWallet - Accept custom network on
signMessage - Add
isMultiWalletmethod - Add
getAuthProviderto wallet provider - Add
getAuthNetworkto wallet provider
pr closed time in 24 days
startedatlassian-labs/compiled
started time in 24 days
push eventarcadeum/ethgas-app
commit sha ab87ab0e306104d9095b826ecb357d12a6e8e7d0
minor
push time in 24 days
push eventarcadeum/arcadeum.js
commit sha c6d0349cc149af4e649197005b6720e73715a0a7
provider: export WalletProviderConfig
push time in 24 days
startedbryan-hunter/yarn-workspace-lerna-monorepo
started time in 25 days
startedkentcdodds/babel-plugin-macros
started time in 25 days
issue closedgo-chi/chi
Hi,
Maybe I might have missed but couldn't see anything so just asking. Are we able to name the routes - similar to this? See example below for better explanation.
Thanks
// Set
r.Post("/users", createUser).SetName("create_user")
// Get in the controller
...(w http.ResponseWriter, r *http.Request) {
name := chi.RouteName(r)
}
closed time in a month
BentCoder
issue commentgo-chi/chi
Thanks for the request, but chi's goals are to remain a minimal router and we wouldn't increase the feature set for named routes.
If you'd like something like the above though, you can pull it off with your own custom middleware and use r.With(SetName("create_user")).Post("/users", createUser) .. this would work out of the box now. https://github.com/go-chi/chi/blob/master/middleware/value.go#L9-L17 here is a simple middleware you could adapt.. but if you wanted to use middleware.Value directly for the above you could do ..
comment created time in a month
push eventgoware/s3up
commit sha 04738494417dff2c20244cfa5a002a411c478fd2
fix base64 encoding, should be base64-url-safe-encoding
commit sha 7508ca47b99f71753da86f5adabd513e865193aa
Merge pull request #10 from goware/base64-url-encoding fix base64 encoding, should be base64-url-safe-encoding
push time in a month
issue commentgo-chi/chi
http.Handler vs http.HandlerFunc
@dvelitchkov I hear you, but the common case is to attach a func SomeHandler(w http.ResponseWriter, r *http.Request) { .. } method to an endpoint, if I change the parameter to a http.Handler it will require everyone to write, r.Get("/path", http.HandlerFunc(SomeHandler)) which I don't think is better. It's been decided for syntactic sugar reasons this is the more common case.
comment created time in a month
push eventarcadeum/ethgas-app
commit sha 0ae269f56e2f9457379d3eb26d0f98797475ebd2
favicon fan request ⛽
push time in a month
created tagarcadeum/arcadeum.js
Javascript & Typescript client for Arcadeum Transaction Relayer, available for Browsers and Node
created time in a month
created tagarcadeum/arcadeum.js
Javascript & Typescript client for Arcadeum Transaction Relayer, available for Browsers and Node
created time in a month
push eventarcadeum/arcadeum.js
commit sha 6736d4eaeff7792ff6f341b5a6a5db34d65e903c
Release v0.3.2
push time in a month
push eventarcadeum/arcadeum.js
commit sha b06d50eccadce025fd5184b6a331450ce09d8d22
Bundle deploy by default on rpc relayer (#45)
push time in a month
push eventarcadeum/arcadeum.js
commit sha d2b875aefba0ca56d8f57c0f30e81329ce6c9fd7
update chaind.gen.ts (#43) * update chaind.gen.ts * fixes * Update chaind client with optional digest Co-authored-by: Agustin Aguilar <[email protected]>
commit sha 766bf06c2e3776191afc12ace92eaf8d50e6792d
Fix decode thershold
commit sha d50625985c83fe6a45dbfd7cb1317e22fc7e6ec5
Add waitForReceipt method (#44)
commit sha 9ba73665ec993424693040fd520349238e4bec4d
release v0.3.1
commit sha 1c2e4fff4c9f4efb542843c7246db2149bb867d4
Remote signers (#39) * Remote signers * Handle remote signers after local signers * Add remote signers and guardd remote signer * Handle empty auxData guardd signer * Skip signer throw on sign
commit sha 6415a27e07862a0801f2a48beb59d8569ad5e4dc
Merge branch 'master' into self-deploy-rpc-relayer
push time in a month
push eventarcadeum/arcadeum.js
commit sha 1c2e4fff4c9f4efb542843c7246db2149bb867d4
Remote signers (#39) * Remote signers * Handle remote signers after local signers * Add remote signers and guardd remote signer * Handle empty auxData guardd signer * Skip signer throw on sign
push time in a month
PR merged arcadeum/arcadeum.js
- Add support for
remoteSignerson Arcadeum wallet - Remote signers sign after local signers, local signatures are included in the payload for remote signers
- Implement guardd remote signer
https://github.com/arcadeum/wallet-guard
pr closed time in a month
push eventarcadeum/arcadeum.js
commit sha 9ba73665ec993424693040fd520349238e4bec4d
release v0.3.1
push time in a month
push eventarcadeum/arcadeum.js
commit sha d50625985c83fe6a45dbfd7cb1317e22fc7e6ec5
Add waitForReceipt method (#44)
push time in a month
issue commentupper/db
upper/v4: consider exposing SetTxOptions
sounds like a good idea. can you guys submit a PR?
comment created time in a month
startedMattiasBuelens/web-streams-polyfill
started time in a month
startedhorizon-games/blender-addon-horizon-tools
started time in a month
issue commentethereum/EIPs
ERC-1654 Dapp-wallet authentication process with contract wallets support
hey all, this might be relevant to check out: https://github.com/arcadeum/ethauth.js / https://github.com/arcadeum/go-ethauth -- it is an authorization scheme using eip712 which supports EOA's and contract wallets implemented in both Typescript and Go. The idea is a dapp makes an auth request of some claims (dapp name, expiry, origin domain), asks a wallet to sign the payload with eip712, and then encodes an ethauth-proof string. You can use the ethauth-proof directly even as an http handler/middleware, but since for contract wallets you need to call isValidSignature remotely, its not ideal to do the check per request. Instead you can think of it somewhat like OAuth, and use the ethauth claims proof and exchange it for a JWT token.
comment created time in a month
push eventarcadeum/arcadeum.js
commit sha d2b875aefba0ca56d8f57c0f30e81329ce6c9fd7
update chaind.gen.ts (#43) * update chaind.gen.ts * fixes * Update chaind client with optional digest Co-authored-by: Agustin Aguilar <[email protected]>
push time in a month
push eventarcadeum/arcadeum.js
commit sha 8f71803a45cbebf3dae07831094aa195730d7cf7
fixes
push time in a month
issue commentgo-chi/jwtauth
Move away from unmaintained dgrijalva/jwt-go
oh cool, thanks for pointing that out. Strange interface though
comment created time in a month
issue commentgo-chi/jwtauth
Move away from unmaintained dgrijalva/jwt-go
https://github.com/lestrrat-go/jwx is another option, and it supports custom claims. For others if you can have a look at jmx, its the likely candidate I will migrate
comment created time in a month
issue commentgo-chi/jwtauth
Move away from unmaintained dgrijalva/jwt-go
thanks @adamchalmers for bringing up the issue. I'd definitely like to migrate to a underlining jwt pkg that is better maintained, especially around security concerns. I took a look at square/go-jose and was starting to integrate it into jwtauth this morning when I realized that it doesn't support custom jwt claims, which is certainly problematic. Looks like neither v2 or v3 of go-jose/jwt support custom claims, but let me know if you see how to do it
comment created time in a month
startedsquare/go-jose
started time in a month
push eventarcadeum/ethkit
commit sha a12d0956eb6f24b145cc3e1e88c42aeb2298727b
ethrpc: ChainID to check if local host and calls NetworkID instead due to ganache bug
push time in a month