CodeTour
CodeTour copied to clipboard
LefterisXris
IntelliJ Plugin
## This is a generic list, with notes (bullet list) of issues/features to work on. - [x] #37 - [x] #38 - [x] #36 - [x] #33 - [x] #44...
Currently all tour files are being stored in the default directory `.tours` under the active project. Let's provide an option to the user to change this to any location they...
`Active` Tour, is currently defined, based on the selected Step. If a tour doesn't have a step yet, it can't be active. Let's provide this option to the users
Currently, if a User wants to create a new Tour, they should select the Root Node from Tours Pane. It would be much more easier and intuitive if we made...
Steps' structure should not be strict. e.g. A step should act like a tour if there are some sub-steps below it. This requires Structural changes. Example Tree rendered Structure: ```...
Current pull request contains patched `CHANGELOG.md` file for the `v0.0.10` version.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "github-actions[bot] avatar"){kind=avatar}
As CodeTour plugin is in very early development stage, it is very likely that its structure will change. That means, that `Tour` and `Step` classes may change and the persisted...
Steps currently require a file:line location reference. We could support navigating on a folder, which will open the `Project` Tool Window and select the target directory. For example, a Step...
Let's provide some demo tours for the following cases: - [ ] Introduction to project - [ ] High-level overview of a project - [ ] Backend API project (e.g....
Currently the CodeTour plugin works with a `file:line` reference. However this seems to be fragile and not easily maintainable as code will change sooner or later and Step's lines won't...