OCTO:New and Noteworthy/V1.2.1
Jump to navigation
Jump to search
New and Noteworthy in OCTO V1.2.1 (Oct, 18 2023)
| 394 - Enhance Source File API for Efficient Retrieval of Large Source Code | We have optimized the way that very large sources are handled by Octo.
|
|---|
| 393 - Create OCTO Client Service for Solution API | Now, it is possible to disconnect a solution from the item editor.
|
|---|
| 390 - Implement Paging and Context Menu for Task Solutions | We've resolved a user interface issue to enhance your experience. Previously, task solutions and task details were displayed together on a single page, which could become cluttered, especially when solutions were lengthy. Here's how we've made it more user-friendly:
1. Paging Functionality: We've introduced paging, allowing you to navigate solutions easily. Now, you can move through the solutions one page at a time, making it less overwhelming.
|
|---|
| 382 - Adding Connect Menu to Each Component View Item for Object-Task Connection | We've successfully enhanced our component view as requested, allowing users to establish connections between objects and tasks easily.
|
|---|
| 371 - Enhance Source Editor in OCTO to Support Editing and Saving of Source Content | Previously, users could only view source code content within the integrated source code editor. You can edit and save modifications directly within OCTO's source code editor.
|
|---|
| 366 - Implement UI for Promote/Checkout Process | You can now conveniently perform promote and checkout processes from both tasks and solutions.
|
|---|
| 58 - Octo - Allow organization ownership edition | The organization admin panel has been revamped to show owners per organization.
|
|---|
| 361 - Add Octo welcome page | As an Octo organization owner or admin, you can let Octo show custom page to welcome new members.
|
|---|
| 380 - Octo client - Add dynamic UI walkthrough | We've added a brief walkthrough steps or tour to introduce new Octo users to main functionalities of Octo and its plugins.
Example of a tour of the main menu and its trigger button:
Example of a tour of the work-management plugin and its trigger button:
|
|---|
| 386 - Octo client - Revamp the URL API page | We've revamped the Octo URL API page for more legibility and ease of use:
|
|---|
| 378 - Octo client - Add the 'About Octo ' page | We've added an About Octo page that will hold core info about the current Octo build instance, info such as current version.
|
|---|
| 339 - Docker image for octo | A Docker image has been created for the Octo server software. The Octoserver Docker image is based on Ubuntu 20.04, Node.js, MongoDB and of course the Octoserver application. The image can be deployed to Windows with support of the Docker Desktop App and any Linux system supporting docker. The Docker image and accompanying documentation will soon be be made on our Octo download page.
|
|---|
GUI issues/enhancements resolved
- 358 - Octo - Allow organization ownership edition
- Make it possible to add/remove organization owners in the Octo admin.
- 359 - Octo client - Only show organizations to members
- In the Octo admin, only a member should be able to see an organization.
- 361 - Add Octo welcome page
- An Octo plugin to edit a welcome page to view per organization.
- 362 - Octo client - The bottom panel of the perspective not showing up
- The bottom panel of the perspective is not showing up correctly. The latter doesn't show up when this bottom tile contains a plugin. Otherwise, the link to install a plugin is not showing up.
- 367 - Allow a plugin to omit itself from the install list
- An Octo plugin can choose not to show up in the install list.
- 368 - Allow a plugin to reject co-install in the same view
- An Octo plugin can require to be the only plugin installed in a given tile/view.
- 369 - Backend Task Programmer Link Overlaps with Clickable Dropdown Menu Area
- When clicking on the dropdown task menu, the backend programmer link appears to be clickable within the dropdown menu area. This results in the backend programmer link overlapping with the dropdown menu, making interacting with the dropdown options difficult. Ideally, the dropdown menu should completely cover the backend programmer link to ensure smooth and intuitive user experience.
- 370 - z-index Issues Encountered When Attempting to Initiate the Transfer Wizard from the Parent Component
- When attempting to initiate the transfer wizard from the parent component, several z-index-related problems arise within the user interface (UI). The transfer wizard UI elements are not displaying as expected in relation to other components and elements on the page.
- 372 - Octo client - Allow a plugin to hide its whole toolbar
- Allow a plugin to instruct the core to hide/show the whole local toolbar (including the plugin name) conditionally.
- 373 - Octo client - Add a 'Save All' menu contribution entry to the core
- Allow a plugin to contribute a 'Save All' action using the core menu contribution mechanism.
- 374 - Enhance Source Editor in VSCODE to Support Editing and Saving of Source Content
- As of the current version of VSCODE, users can view the source code content using the integrated source code editor. However, a significant limitation exists: the source code editor cannot facilitate editing and saving modifications to the source code.
- 378 - Octo client - Add the 'About Octo ' page
- Add a page to the Settings section to show info about Octo
- 379 - Octo VSCode - Give the option to open a file in read-only mode
- When using Octo file system in VSCode, give the option to open a file in read-only mode.
- 380 - Octo client - Add dynamic UI walkthrough
- A dynamically built user tour to introduce main functionalities of Octo core or plugins. Tour steps should be read from declaratively added HTML attributes.
- 381 - Create OCTO Client Service for Connection List API
- This issue aims to develop an OCTO client service for the Connection List API. This client service will enable efficient and seamless communication between the client-side applications and the Connection List API.
- 383 - In a lot of components, the error alert does not show the details of thrown OctoError
- When an OctoError is thrown within various components of our Octo, the error alert message displayed to the user lacks essential details about the error itself. This lack of information hinders both users and developers in understanding the root cause of the problem and resolving it efficiently.
- 384 - The URL Tracker of the Source Editor Does Not Work Anymore Due to the Latest API Changes
- We have successfully addressed the underlying issues that were causing the URL tracker feature within the source editor to malfunction, ensuring that it is now fully operational.
- 385 - Add help tour to the perspective creation wizard
- Add more explanatory help to the perspective creation wizard.
- 386 - Octo client - Revamp the URL API page
- Revisit the URL API UI for more visibility and user-friendliness.
- 387 - Octo client - Add help tour to work-management UI
- Add explanatory help to the work-management plugin UI when needed for a smoother user-experience.
- 388 - Octo client - Organization and perspective info toasts not showing up
- Clicking the organization and perspective info toasts button not functioning.
- 389 - R&D: ANTLR and grammar parsers
- R&D: RPGLE ANTLR grammar/lexer integration with VSCode language server.
- 391 - Integrate the ANTLR4 code with the Octo language server
- Generate the Typescript code from the ANTLR4 parser and lexer. Then integrate the transpiled code in the Octo VSCode language server.
- 392 - Integrate the Octo VSCode file-system with the language server
- Octo VSCode extension uses its own file system implementation to handle files. Octo embedded language server needs this capability of seeing and reading such files while handling requests from the Monaco editor. Hence, the integration of this file system into the Octo embedded language server.
- 395 - Octo - Implement LSP code completion
- Add the first stage of RPGLE code completion implementation of LSP specs.
- 396 - Octo client - tour UI malfunctions
- The tour UI steps don't hide in some conditions.
- 397 - Octo server - strip out the password form mail failure
- When sending a test mail from Octo admin fails, Octo server should strip out the password from the error response.
- 398 - Octo client keeps loading when first installed
- Upon install and first sign-in, Octo client does't show the expected prompting link to create a perspective. It keeps showing a loader instead.
- 403 - Save Menu in Source Editor Remains Disabled After Changing the Source
- The "Save" menu option in the source editor now becomes enabled, as indicated by a green color and blinking, just as expected. The necessary attention and resolution have been applied to ensure the proper functionality of this feature.
- 399 - Source couldn't be open
- We have to either fill the object code or ifs path not both at the same time.
- 400 - Member attribute is not correct.
- Member attribute was not correctly shown.
- 401 - Change the header caption.
- We need to change the login header caption to "IBMi Login" instead of the component name.
- 405 - Action type Promote fails with multiple solutions
- The task with multiple solutions in different environments was not working as expected with action type PROMOTE.
- 406 - Programmer not filled in
- The programmer drop down is not filled in. It should also contain UNASSIGN which should be the value '*PGMR'.
- 407 - Error Alert Doesn't Display API Response as Title
- The current error alert mechanism in our application is not functioning as expected. When an API call returns an error response, the error message retrieved from the response is not being displayed as the title of the error alert. This inconsistency in the alert title can confuse users and hinder their ability to quickly identify and understand the nature of the error.
- 408 - Show the active solutions in the Object component.
- The active solutions are displayed in the Object component.
- 409 - Show the source location in the object component
- The source location is displayed in the Object component.
- 410 - Octo VSCode - Make of the Octo LSP server an extension
- Package the Octo RPG LSP server as a VSCode extension that can be separately published and installed in VSCode Market.
- 411 - The item editor triggered from task-tracked URL does not populate the programmers list
- When an item editor is triggered from a task-tracked URL, it should automatically populate the programmer's list with the relevant information.
- 413 - Promote Task Always Generates a Response, Even if it's an Error, but Response Data Contains Information About Error Status
- When using the "Promote" feature in our application to transition a task to a different state, it appears that a response is generated regardless of whether the action was successful or resulted in an error. However, the response data contains valuable information that allows us to determine if the response indicates an error or not. This behavior could be confusing and less intuitive for users who expect responses only in successful cases.
- 414 - Add Octo VSCode extension pack
- A VSCode pack extension allows the un/install of multiple extensions from the VSCode market in one go. In our current case, a pack would install, both extensions, the TD/OMS work-management and the Octo RPG language server extensions.
- 417 - Octo VSCode - Remove unnecessary files when packaging the VSIX
- To minimize the VSIX file size, ignore the assets that are only relevant when deploying the Octo client to Octo server but are not so when packaging it as a VSCode extension (.vsix).