Management of the view after adding the section in the page , so when using it to mint

[akramsarkis]

• [x] When you Mint using the Whitelist CTA, you will call the API done backend by sending the Wallet id, the whitelist id ( The one of the new app created backend, not the index of the contract )
• If the address is not in the whitelist you will get an error message
• If the address is in the whitelist then you will get the proof that you will need to add to the transaction with the token id, the whitelist index , the number of token, the proof and the value of ETH you will send
• [x] Note that for the calculation, number of max, etc you should use the same management as for the bloc we already have
• [x] Now if the public minting is off , You need to check if the whitelist minting is on and if so only this one will show to the user
• If Both public and whitelist are off, then message should show to the user that it is not open yet for minting

[mahfouzhseineweev]

The issue took more time than expected and still need 3h because of the following:

The expectation was to only fix a bug on the configurable section and have it ready to be implemented with the nft section and then complete the rest of the points in the issue. But as a result I found that the configurable section was built in a completely different way than what we expected. And it has a lot of problem to be fixed and to be compatible with the updates done on the whitelist API. Which is why it is taking more time. This is in plus of multiple blocking points that has been encountered while working on the configurable section such as the render API call and the edit section page problems that needed multiple debugging sessions to find the problems and fix them.

[akramsarkis]

@jfayad this can be closed