We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nowadays it is quite common to create API pages. It would be nice to use a folder for the APIs, instead of using the Page folder.
Perhaps a parameter can be added to indicate if a different folder is used for the APIs, using the default API as a folder name.
Best regards,
The text was updated successfully, but these errors were encountered:
Hi, we use the following way to group API pages:
// in .vscode/settings.json or your.code-workspace "explorer.fileNesting.enabled": true, "explorer.fileNesting.expand": false, "explorer.fileNesting.patterns": { "*.report.al": "$(capture).report.rdl, $(capture).report.docx, $(capture).report.xlsx", "*.reportext.al": "$(capture).reportext.rdl, $(capture).reportext.docx, $(capture).reportext.xlsx", "_APIPageContainer.txt": "API*.Page.al", // <------------------ "_APIQueryContainer.txt": "API*.Query.al", // <------------------ },
So if you create a file named _APIPageContainer.txt in pages folder all pages starting with API will appear to be under _APIPageContainer.txt.
This only works in inside VS Code though.
Sorry, something went wrong.
No branches or pull requests
Nowadays it is quite common to create API pages.
It would be nice to use a folder for the APIs, instead of using the Page folder.
Perhaps a parameter can be added to indicate if a different folder is used for the APIs, using the default API as a folder name.
Best regards,
The text was updated successfully, but these errors were encountered: