Add ERC721 preset

[andrew-fleming]

Fixes (partial) #804 and #693.

PR Checklist

• Tests
• Tried the feature on a public network
• Documentation

[ericnordelo]

I think we should swap the components to make ERC721 appear first (this applies to impls below too). That is consistent with the Account Preset as well.

[andrew-fleming]

I agree in the sense that it's the "main" component, but I switched it because Access appears first in the imports and IMO it appears more organized that way. What do you think?

[ericnordelo]

mmm, got your point, but I still think it makes more sense to have the main component first, instead of letting the imports decide. We still need to define the rule for this, but I don't like the one coming from import orders that much 😢

[andrew-fleming]

That's fair, and we also already have the account preset using the suggested approach. I'll update and we can maybe revisit in the future

[martriay]

i actually like SRC5 first, as it's a dependency of ERC721. also, not sure if there's always going to be a "main component", and it's not clear to me that's a concept we want to suggest or push.

+1 to not inheriting order from imports

[andrew-fleming]

also, not sure if there's always going to be a "main component", and it's not clear to me that's a concept we want to suggest or push.

+1 to not inheriting order from imports

Let's say we create an ownable, pausable ERC20 preset. There's no component dependency like with SRC5. If we're not using the main component approach and we're not inheriting order from imports, how else can we organize the component declarations?

[martriay]

maybe we don't need a rule for that

[ericnordelo]

Besides perhaps the XYZ discussion for changes pending to be released, I think this is good to go!

[martriay]

Nice work! Looks good to me.

Opened an issue to track adding it to the docsite.

[martriay]

Looks good. Thanks!