Sohrab

We will tackle the client-side of this later but here are some considerations: * Make fields in external representation optional, where it makes sense, and remove them prior to serialisation...

How about `ENTER` to jump down to next account field (if auto-complete is not open)?

Basic functionality has been implemented. We need to add more content to the suggestion list: * Top token mints * Common market accounts * Validators * Etc.

This sounds like a question for the Discord. I've seen dynamic allocation done by airdropping another NFT or SPL Token that they can burn to mint. Or off-chain validation with...

I have also observed this with `useRouter.refresh()`: ```ts useEffect(() => { new PerformanceObserver((list) => { if ( (list.getEntries() as PerformanceNavigationTiming[]).find( ({ type }) => type === "reload" ) ) {...

What makes this quite cumbersome is that say if I have `AccordionItem`s that do not render due to some logic inside them, now all that logic needs to be pulled...

Ok, I think I know what's happening here. [This part of the macro](https://github.com/project-serum/anchor/blob/59c2dbb71293a380baefabeecfe7167aedbf061f/lang/syn/src/codegen/program/accounts.rs#L49) always assumes that all accounts are visible at the crate level. However in our use case, the...

[Browser and runtime support](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat/format#browser_compatibility) seem decent (except Deno): `intl-messageformat`, or rather `intl-numberformat` does seem to only support number atm. I asked the question over there as well: https://github.com/formatjs/formatjs/discussions/4699