-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
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
Add plugin: Plugin REPL #5050
base: master
Are you sure you want to change the base?
Add plugin: Plugin REPL #5050
Conversation
Hello!I found the following issues in your plugin submission Errors: ❌ Please don't include This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it. |
This should be fixed |
The automated review has not found any issues with your code, ready for manual review. |
Hello!I found the following issues in your plugin submission Errors: ❌ Could not parse " is not valid JSON This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it. |
The automated review has not found any issues with your code, ready for manual review. |
Hello!I found the following issues in your plugin submission Errors: ❌ The newly added entry is not at the end, or you are submitting on someone else's behalf. The last plugin in the list is: This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it. |
Hello!I found the following issues in your plugin submission Errors: ❌ Please don't include This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it. |
The automated review has not found any issues with your code, ready for manual review. |
To make the manual review process and future plugin maintenance more efficient, we recommend that you move all source code files into a this.app.workspace.on('active-leaf-change', () => { plugin.loadInit() }) let vaultPath = this.app.vault.adapter.basePath id: 'repl-enter',, id: 'repl-exec',, id: 'repl-prompt-exec', app: any, app: any, app: any, app: any, app: any, editor: any, app: any, app: any javascript, Javascript |
Done in:talwrii/plugin-repl@2959a57
Done in: talwrii/plugin-repl@7acf21f
Done in: talwrii/plugin-repl@2da8195
Done in: talwrii/plugin-repl@7c8b88b
Done in: talwrii/plugin-repl@e1e1360 Sometimes I'm using methods and properties (particularly related to plugins and commands) which aren't part of the documented API, which was part of the reason I was using any. I've implemented my own "PrivateApp" interface which adds these methods. Is there an analogue of Okay, I've given the new version a test and cut a new release: https://github.com/talwrii/plugin-repl/releases/tag/1.0.3 |
fix up name. "Automate the thing that shall not be named"
fixup descriptoin
add back plugin (i accidentally removed it)
fix up description (again)
I did a force push (after rebasing onto upstream master) because there were complaints here about a rebase merge being impossible. |
Thank you for your submission, an automated scan of your plugin code's revealed the following issues: Required[1]:You should not cast this, instead use a Optional[1][2]:Casting to Do NOT open a new PR for re-validation. |
I fixed the "as warnings". I'm still using "as casts" for some interfaces (specifically the wrappers I have for Templater and dataview) - the linting script Obsidian is using seems to allow those. There does not seem to be a way to "test for" interfaces at runtime. |
I am submitting a new Community Plugin
Repo URL
Link to my plugin: https://github.com/talwrii/plugin-repl
Release Checklist
main.js
manifest.json
styles.css
(optional)v
)id
in mymanifest.json
matches theid
in thecommunity-plugins.json
file.README.md
.