tfelix / w3shop Goto Github PK

To give the user a nicer feeling when buying an item, some more feedback or animations would be great after the buy TX was signed. Possibly look into the Bootstrap NGX animations library to give the user more feedback something is going on.

• User is shown a current "Waiting..." page after TX was signed
• User gets a nice success animation when the buy process was successful

When the owned item page was once resolved, re-visiting again triggers the resolving of the items. This wastes resources and slows down the whole process. Usually this does not really change and can be cached.

After an item purchase this case should be invalidated.

When items are successfully bought, the shop displays an error.
Also in general the success message of the bought items is missing.

This is caused because there is a bug in the sum function that calculates the total pricing of the checkout component. Cart is set to an empty array after the buy process, but this fails the price calculation function resulting in an error.

When the shop was initially created this URL seems to be set incorrectly.

See: https://arbiscan.io/tx/0x0d88c2c11712e358ae5d8f6e94fcc7737aeece8b2487c1c03ba090863b15a525

Implement the form to generate new shop items collections.

The latest version has an improved ESM support and can be bundled much smaller that will result in much shorter shop loading times.

When the user enters a shop and his wallet is connected, but on a wrong network the page looks broken and bad error messages pop up.

Expected Behavior:

• User should see a better error message
• Remove broken elements like shop name and the empty footer as no data can be requested.

Description text states a comma should enter the keyword. Instead spaces are used. This is confusing.

After the users has loaded a shop info, when he switches the network afterwards this breaks the UI because the error message is shown again.

It would be better if the already loaded data is hold and only a smaller error is shown when the users wants to actually interact with the chain.

Story
As a shop owner
I want to set aside a percentage of the user payment that they get refunded
when they later leave a review for the article.

One possible option is

State holding intermediate contract

• Contract keeps the users fee for a certain amount of time
• Holds the state of the user bought item (can the user proof this to the contract so state save is not required?)

Pro

• Shop owner can later change comment subsidized percentage easily without affecting open and waiting comment returns

Cons

• Swiping funds of expired comment windows is complex and requires a lot of gas
• Possibly a lot of data must be kept in the contract (bought item, token? (or always pay in ETH?)

Enables Wikis as a means of documentation and also link them on the footer.

• Create twitter account and link it
• Rename the Orbis group
• Link to github wiki as documentation when repo is public and wiki page can be added

This contract should be verified: https://arbiscan.io/token/0x0781cb62a209f1f38c3ca0fc554c1cbe8f447f39#code

You either need to extract the input file or compile and submit it for identification to Arbiscan.

Write a welcome and explanatory text on the front page.

When you start on the wrong network and switch to the Goerli Testnetwork by clicking the message in the alert box, after the switch is completed the alert box stays visible.

Its expected to be hidden after the successful switch.

Issue

The complex URLs that are required to fetch shops contents and bootstrap the client only app are hard to remeber: https://w3shop.eth.limo/#/s/AQAApLEHgctiognx84w8oPxVTBy_j0R-OQ

It would be nice to have subdomains available for shops to register in a self service like fashon, that allows the redirection towards the actual shop. It could look like https://awesome-shop.w3shop.eth

Solution

• A smart contract could handle the creation of w3shop.eth subdomains for shop owners.
• A special field in the name could hold the hashcode of the shop in question. This should be an immutable field for the user. If this can not be done with ENS a lookup contract could hold the link ENS Name -> shop address
• The subdomain should point its IPFS address to a bootstrap shop that will detect it was loaded by a subdomain and then start the bootstrap prozess: 1. fetch contract via either ENS field lookup or via lookup contract, load the regular bootstrap prozess.

Blockers

• Arbitrum ENS Support - So far ENS only operates on mainnet making the interaction complex as the w3shop lives on Arbitrum. The support for L2 Resolvers first must be solid with documentation.

When a shop is closed or transferred its ownership there is no indication that currently a TX is ongoing. It also does not gray out the transaction button so the user potentially clicks twice.

Make the buttons grayed out and maybe use a spinner/waiting indicator. Try to make the indicator re-usable.

Library seems not well maintained and it also has old angular dependencies, making upgrading harder. Replace it by a custom coded wizard.

• Add Profile Image and Header
• Check profile description
• Tweet a hello world after launch

Since we must support localhost as well as the loading of assets via IPFS, we must handle baseHref in a very strange way.

For more information or ideas regarding this topic see:

• https://symflower.com/en/company/blog/2021/path-independent-angular/
• https://shekhargulati.com/2017/07/06/angular-4-use-of-base-href-and-deploy-url-build-options/
• http://www.projectcodify.com/angular-set-base-url-dynamically

• Write a cronjob on the sever that automatically detects new files and deploys them to IPFS as a IPNS.
• Fix CI build process

OpenSea as issues identifying the first test item. When the contract is verified and the URI can be requested of this token debug it.

When the file gets downloaded it currently needs to go through Filesaver.js this library states different safe sizes for varioud browsers: https://github.com/eligrey/FileSaver.js/

We should aim for max. compatability and limit shop owners atm to file uploads < 500MB.

Find a way to create and display a version number or commit hash for the deployed page.