Replies: 2 comments 4 replies
-
I love it! You might also want to check out other recommendations for API pages, as documented on https://alguidelines.dev/docs/bestpractices/api-page/ ? Some examples:
|
Beta Was this translation helpful? Give feedback.
4 replies
-
Btw, AZ AL Dev Tools has a nice feature when you create API pages, as mentioned in anzwdev/al-code-outline#528 (comment), so you do get the naming above by auto-magic 🙂 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
When creating API endpoints I tent to expose the
"No."
fields as number, with the idea that whoever consumes the API does not know the inner workings of Business Central and that there no possible ambiguity between No (boolean) and Number.For Example:
This is inspired by the way Microsoft has created the default API's: https://github.com/StefanMaron/MSDyn365BC.Code.History/blob/b7f963bfbf1ca844150d40bd13062c8a3d8e5cd9/APIV2/Source/_Exclude_APIV2_/src/pages/APIV2Accounts.Page.al#L34
I'm thinking of having a rule to apply the best pratices on naming.
The difficulty here is to have this a generic as possible, I think these rules below could always be applied?
Beta Was this translation helpful? Give feedback.
All reactions