update for isAction

[Mustachedom]

no sense in having

 data[#data = 1] = {
    data.params.event[?]
}

if you are just utilizing a function with this PR you can do

exports['qb-menu']:OpenMenu({
{
header = 'hello',
isAction = function()
 print('hello world')
end
}
})

Describe Pull request
ideally this will make things easier on devs since it will greatly reduce the tables needed to make a menu **if they are using an isAction = function() **

instead of doing

 for k, v in pairs (data) do
            jobs[#jobs + 1] = {
                header = 'Job: ' .. v.label,
                txt = 'Rank: ' .. v.rank .. ' | Salary: $' .. v.pay,
                params = {
                isServer = true,
                event =  'qb-multijob:server:changeJob',
                    args = {
                        job = v.job,
                        rank = v.level
                    }
                }   
            }
        end

They can now do

 for k, v in pairs (data) do
           jobs[#jobs + 1] = {
               header = 'Job: ' .. v.label,
               txt = 'Rank: ' .. v.rank .. ' | Salary: $' .. v.pay,
              isAction = function()
                TriggerServerEvent('qb-multijob:server:changeJob', {job = v.job, rank = v.level})
           }
       end

While still maintaing the older method with a bunch of tables so it will be backwards compatible for other scripts

Questions (please complete the following information):

• Have you personally loaded this code into an updated qbcore project and checked all it's functionality? [yes] (Be honest)
• Does your code fit the style guidelines? [yes]
• Does your PR fit the contribution guidelines? [yes]

[Cocodrulo]

There is a whitespace after the then, just for the linting report to pass

[Cocodrulo]

The rest of the PR looks great to me, only that yo should edit the PR comment to point out that is not isAction anymore, now is just action.

[Mustachedom]

good looking out @Cocodrulo this is why i dont push edits in bed way past my bedtime

[Mustachedom]

#update

no sense in having

 data[#data = 1] = {
    data.params.event[?]
}

if you are just utilizing a function with this PR you can do

exports['qb-menu']:OpenMenu({
{
header = 'hello',
action = function()
 print('hello world')
end
}
})

Describe Pull request ideally this will make things easier on devs since it will greatly reduce the tables needed to make a menu **if they are using an action = function() **

instead of doing

 for k, v in pairs (data) do
            jobs[#jobs + 1] = {
                header = 'Job: ' .. v.label,
                txt = 'Rank: ' .. v.rank .. ' | Salary: $' .. v.pay,
                params = {
                isServer = true,
                event =  'qb-multijob:server:changeJob',
                    args = {
                        job = v.job,
                        rank = v.level
                    }
                }   
            }
        end

They can now do

 for k, v in pairs (data) do
           jobs[#jobs + 1] = {
               header = 'Job: ' .. v.label,
               txt = 'Rank: ' .. v.rank .. ' | Salary: $' .. v.pay,
              action = function()
                TriggerServerEvent('qb-multijob:server:changeJob', {job = v.job, rank = v.level})
           }
       end

While still maintaing the older method with a bunch of tables so it will be backwards compatible for other scripts

Questions (please complete the following information):

• Have you personally loaded this code into an updated qbcore project and checked all it's functionality? [yes] (Be honest)
• Does your code fit the style guidelines? [yes]
• Does your PR fit the contribution guidelines? [yes]