use-ink / link Goto Github PK

Ideally, when you navigate around or refresh the page the same account should be selected in the dropdown. If the account doesn't exist anymore, it should default to the first account found.

After a successful transaction, both chain and contract events should be shown.

Before:

Now:

Currently, descriptions are only in the placeholder.

So no decentralized entry point.

To reproduce:

1. Paste an URL
2. Delete letters from the alias field so that the error is shown
3. Type more letters in the alias field
4. See incorrect error for a brief second

The connected state is lost after page refresh.

We should use the concrete address from the wallet instead of YOUR_SS_58_ADDRESS to make it copy paste able.

When a user tries to go to tiny.ink/some-non-existing-slug the app doesn't do anything.
This is an older issue, unrelated to useInk migration

Using this:

A links overview page was introduced here #20 but i removed it from the MVP.
I think it might be cleaner to use react-router instead of HeadlessUI tabs, but the layout can be copy-pasted.
Maybe we should limit to displaying 15 links, the list can grow fast.

Is there a way to get all the links shortened by an account from contract storage?

• Add resolve function
• Add shorten(slug: Vec<u8>, url: Vec<u8>) -> Result<()> function, assert that len >= 5.
• Make it upgradeable with a multisig using a proxy account

Shorten an URL and then follow the generated link. A URL not found error message is shown incorrectly before actually redirecting

• Implement mockup.
• Use substrate-connect to resolve the URL.
• Forward in the browser.

It displays an empty div when clicking connect without having an extension installed or not permitting the extension to connect.

The waiting time for a shorten transaction to finalize is longer than 12s in the UI, meaning something is lagging somewhere
Also the resolving takes up to a few seconds sometimes and it used to be faster

Use one of the npm packages to make sure the URL we forward to does no shenanigans.

• Should be a proxy account on-chain + multisig with us contributors.

• Implement the mockup MVP.
• Issue a dry-run RPC to see if the shorten function will succeed.
• If it succeeds issue the transaction.

Would be nice to allow people to drip funds in their account directly from the app. Needs design.

After a page reload the selected address is always set to the first entry. The selected address should be persistent across reloads.

Show some info during the resolve process about forwarding which is happening.

• Should use capi.
• Figure out where to host it.

The account dropdown is pushing down the main card. Seems to be fixable by removing the fixed position and top margin of the close button.

Currently we assume users have the Polkadot.js extension in their browser. Other wallets haven't been tested.
The user experience is very poor for first time users. There is no guide to install a compatible extension and create a new account.

If the user already pasted a URL in the field and connects the wallet via the button below, all inputs and submit button are disabled.

Note: doesn't happen if the user connects via the top right corner button or if the form is empty when clicking the button.

• So "call contract dry-run"

The wallet connection flow goes doesn't handle the possibility of the user not having set up an account yet. Clicking on the "Connect to... " button doesn't do anything.
Noticed this on Firefox, where there are no imported accounts in the pjs extension. Not sure if it's browser specific.

I am using the live version here: https://tiny.ink/

I have Polkadot-JS extension installed, with valid accounts, and tried in both Brave and Chrome.

I have tried this both before and after connecting my wallet, but I see the same behavior.

TO REPRODUCE:

1. Visit page
2. Enter any URL in the textbox labeled "Paste an URL to get cost estimations" - for example, "https://en.wikipedia.org/wiki/Cockatiel". Alternatively, you can start typing and the same behavior will occur after a few keystrokes.

EXPECTED BEHAVIOR:

1. User can then click "Shorten"

OBSERVED BEHAVIOR:

1. Page becomes entirely blank (only purple background)