Page Designer - New Extension
Simple sort of bug to work around, but if you've created a new workspace/extension, and have not yet hit Package, you can't open the Page Designer, as the GUI crashes trying to load from translations that don't exist yet.
Translation Ref Paths - Error handling
I didn't quite know what you meant by "fully qualified path" for the translationReferencePaths setting (example in tooltip, maybe?). So, my first few attempts were wrong - so wrong that "AL Home" doesn't open, doesn't give any error messages, anything.
Page Designer - Extension Dependency
I created an Extension ("A") that adds a Group to the Layout of the Item Card. Then, I created a 2nd Extension B that depends on A. It does "addlast" to add to the Group from A on the Item Card. This renders correctly in BC, but the Page Designer doesn't
"Add Project" - Related to #135
The "Create Workspace" has lovely functionality to quickly "Add Project" for multiple new extensions. I've had a few situations where I've needed to make 3-4 new extensions in an existing workspace at once, and it'd be really neat to get "back" to the
New Workspace - Use Relative Paths
In the "Create AL Workspace" functionality, it uses the local full filesystem paths (like "C:\repos\something\ext1" rather than relative to the folder (like "ext1"). This makes the workspace file non-portable between environments.
Could use a little guidance on Page Designer
First off, it's amazing. 100%. I'm a little confused by the tool, though. I'm in a multi-extension workspace that I have lots of pre-existing code in. I open a CustomerCard page extension object from one of them. I get the phenominal layout, overview,
Workspace Overview
Something I often am running into as a dev. "What range(s) should I give my new project?" Would it be possible / feasible to have a view that shows an overview in the current workspace? I'm thinking a Tablegrid of: Columns -> Object Types, Rows ->
AL Search preview
Took a quick look at the AL Search, but sadly, no luck taking it for a test drive. Full trace attached. Failed to invoke hub method 'Search'. System.AggregateException: One or more errors occurred. (There is an error in XML document (8, 48).)
Workspace UI Shortcuts
When you have no Workspace open: There's useful Create / Open buttons. When a Workspace is already open, there's no way to access those from the UI. (Obviously, yes, there are still commands for it.) Proposed suggestion: In the [...] Menu, could you
Create Workspace - Required Fields
If you disable the Create Test Project, the test object ranges are still required to be filled in. Additionally, if you click Finish without all 'required fields' filled in, there is no UI information about why nothing is happening. (Such as an error
App.json - Platform & Application
If I use the current AL Extension to do "AL Go!" to create a new extension, and I select the latest version as my target, I get these platform and application versions: "platform": "17.0.0.0", "application": "17.0.0.0", If I Create a Workspace with
app.json - Test App - 0.9.682
I like how the Testing projects spun up by the Create Workspace automatically depends on the Project it's the Test for. But, shouldn't it also have the Testing dependecies?
App.json Typo 0.9.682
I spun up a test workspace using AL Studio 0.9.682. Curiously, the app.json had a typo: "privaryStatement": "", Small thing. Should be "privacyStatement".
General Inquiry: Roadmap
With a powerhouse toolkit like this, I'm sure you've go about a million different ideas of what to work on next, what to add still. Any chance that roadmap might be a visible thing, like a Github Project board? It'd be neat to see "coming soon" and "someday"
General Discussion
General Discussion