Should we require all scopes to be used? about eos HOT 2 CLOSED

This would help. I have this hack in place now, I'm not sure if it will work..

For example:

struct transfer
   from      AccountName  # may not be the message.sender if message.sender has delegated authority by from
   to        AccountName
   amount UInt64

transfer inita initb 1 yields scope: ['inita', 'initb'], authorization: ['inita', ...]

given the following hack:

    {// FIXME Hack, until an API call is available
      const fields = Object.keys(definition.fields)

      const f1 = fields[0]
      if(definition.fields[f1] === 'AccountName') {
        tx.scope.push(params[f1])
        tx.messages[0].authorization.push({
          account: params[f1],
          permission: 'active'
        })
      }

      if(fields.length > 1) {
        const f2 = fields[1]
        if(definition.fields[f2] === 'AccountName') {
          tx.scope.push(params[f2])
        }
      }
}

Does not work with new account.. newacct probably should not be in the scope because it does not exist in the block that the newacct will execute in.

struct newaccount
   creator   AccountName
   name      AccountName
   owner     Authority
   active    Authority
   recovery  Authority
   deposit Asset

yields scope: ['creator', 'newacct'], authorization: ['creator', ...]

So, I need the scope to be automated or done in an API call or I'll start adding these case by case to eosjs. Also, notice the authorizations is something we need too.

from eos.

OBE

from eos.