Rich Text Output Window Not Opening
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 204
- Forks
- 82
- Avg merge
- 22h 27m
- Merged PRs (30d)
- 3
Description
Describe the bug
When I execute /projects lists (or other associated commands) while the plugin is configured to output Rich Text - it yields no output. The plugin will show "Generating Project Review List" and markdown versions (if selected) will be generated not rich text.
To Reproduce
Steps to reproduce the behavior:
- Execute /project lists from the respective plugin menu.
Expected behavior
Outputs the Rich Text version.
Screenshots
NA
System
- Device: MacBook Pro
- OS: macOS Venture: 13.3.1 (a) (22E772610a)
- NotePlan Version: 3.9.1 (1030)
- Plugin Name & Version: Project + Reviews v0.10.1
Additional context
Only that it seems isolated to a particular system / combination. Works on there machines.
Plugin Console Log
To provide us with more clues about where the bug/error is occurring...
- Open the Plugin Console by going to
Noteplan > Help > Plugin Console - Run the plugin you're reporting
- Copy the output from the Plugin Console and paste it below
- Delete any output that has personal information you don't want in there
Executing function 'makeProjectLists'
2023-05-09 08:45:20 | ERROR | Project constructor :: Expected string, got undefined
2023-05-09 08:45:20 | ERROR | Project constructor :: Expected string, got undefined
2023-05-09 08:45:20 | ERROR | Project constructor :: Expected string, got undefined
2023-05-09 08:45:20 | ERROR | Project constructor :: Expected string, got undefined
2023-05-09 08:45:20 | ERROR | Project constructor :: Expected string, got undefined
2023-05-09 08:45:20 | ERROR | Project constructor :: Expected string, got undefined
2023-05-09 08:45:20 | WARN | NPparagraph/getOrMakeMetadataLine :: Warning: Can't find an existing metadata line, so will insert a new line for it after title
2023-05-09 08:45:21 | ERROR | Project constructor :: Expected string, got undefined
2023-05-09 08:45:21 | WARN | NPparagraph/getOrMakeMetadataLine :: Warning: Can't find an existing metadata line, so will insert a new line for it after title
2023-05-09 08:45:21 | ERROR | Project constructor :: Expected string, got undefined
2023-05-09 08:45:21 | ERROR | renderProjectListsHTML :: Expected string, got undefined
2023-05-09 08:45:21 | ERROR | Project constructor :: Expected string, got undefined
2023-05-09 08:45:21 | ERROR | Project constructor :: Expected string, got undefined
2023-05-09 08:45:21 | WARN | NPparagraph/getOrMakeMetadataLine :: Warning: Can't find an existing metadata line, so will insert a new line for it after title
2023-05-09 08:45:21 | ERROR | Project constructor :: Expected string, got undefined
2023-05-09 08:45:21 | ERROR | Project constructor :: Expected string, got undefined
2023-05-09 08:45:21 | ERROR | Project constructor :: Expected string, got undefined
2023-05-09 08:45:21 | ERROR | Project constructor :: Expected string, got undefined
2023-05-09 08:45:21 | ERROR | Project constructor :: Expected string, got undefined
2023-05-09 08:45:21 | WARN | NPparagraph/getOrMakeMetadataLine :: Warning: Can't find an existing metadata line, so will insert a new line for it after title
2023-05-09 08:45:21 | ERROR | Project constructor :: Expected string, got undefined
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing /project lists with Rich Text selected and reviewing the Plugin Console output. Trace makeProjectLists and renderProjectListsHTML, focusing on the repeated "Expected string, got undefined" errors from Project constructor. Done means the Rich Text output window opens and displays the generated project list without those errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- desktop, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100