In larger apps we end up with large number of objects in rather flat structure: 20 files in src/codeunit, 40 in src/pageextension, etc. At the moment even smaller projects look very messy and are difficult to explore:
Microsoft added namespaces in BC23, but that functionality won't be in previous BC versions, so we need some other kind of hint to define the folder structure.
For example:
//crs-al namespace MyProduct.Payments;
table 700000000 "MP My Table"
...
or
namespace MyProduct.Payments;
table 700000000 "MP My Table"
...
Would go into src/MyProduct/Payments/MyTable.Table.al.
Subfolders like table, page, etc are not needed anymore. A particular namespace should have only a few objects otherwise we go back to the original problem.
Hi,
In larger apps we end up with large number of objects in rather flat structure: 20 files in src/codeunit, 40 in src/pageextension, etc. At the moment even smaller projects look very messy and are difficult to explore:
Microsoft added namespaces in BC23, but that functionality won't be in previous BC versions, so we need some other kind of hint to define the folder structure. For example:
or
Would go into
src/MyProduct/Payments/MyTable.Table.al.Subfolders like table, page, etc are not needed anymore. A particular namespace should have only a few objects otherwise we go back to the original problem.
Thanks.