64
R

Warn about insufficient/invalid arguments in a call to the built-in GET procedure

Rob van Bekkum on 5/6/2019 7:52:20 AM
Would like to see that the AL compiler or one of the code analyzers gives a warning when the Get procedure is called with insufficient arguments, too many arguments, or arguments of invalid types that do not match the formal parameters expected given the PK of the record in question.
This is an error that is hard to spot, so I think detection and a warning on this error would be really helpful.
Category: Development
STATUS DETAILS
Needs Votes
Ideas Administrator

Business Central Team (administrator)

Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future.

Best regards,
Business Central Team

Comments

R

R

RE: Warn about insufficient/invalid arguments in a call to the built-in GET procedure

Lars Black on 10/8/2020 2:01:13 PM

I would really prefer codecop rules like this instead of rules like AA0072....

Category: Development

R

R

RE: Warn about insufficient/invalid arguments in a call to the built-in GET procedure

Nicolas Saleron on 12/29/2019 10:49:13 PM

I agree with this proposal but... how would you handle setup table?
For instance GLSetup.Get() should be replaced by GLSetup.Get('') everywhere to prevent getting this warning?

Category: Development

R

R

RE: Warn about insufficient/invalid arguments in a call to the built-in GET procedure

Patrick Schiefer on 7/17/2019 9:25:56 AM

It would improve the development significant

Category: Development

R

R

RE: Warn about insufficient/invalid arguments in a call to the built-in GET procedure

Frédéric Vercaemst on 5/6/2019 9:55:34 AM

Reported on Github as well
https://github.com/Microsoft/AL/issues/4622

Category: Development