It would be more convenient for users of the tool if the edits were triggered directly from the tool itself, rather than via QuickStatements that require them to switch into a separate tool to complete the edits. This is not a v1.0 requirement, but would be a nice feature for a v2.0 of the tool. Just dropping some resources that may be helpful for this: - [OAuth/For Developers](https://www.mediawiki.org/wiki/Special:MyLanguage/OAuth/For_Developers) – Developer documentation for creating tools that can interface with a MediaWiki wiki running the OAuth extension - [Vuetify app with Wikimedia OAuth login](https://addshore.com/2025/02/vuetify-app-with-wikimedia-oauth-login/) — blog post from 20 February 2025 by @addshore - [webapp-clientside-vite-guestbook](https://github.com/lucaswerkmeister/m3api-examples/tree/main/webapp-clientside-vite-guestbook): demo showcasing OAuth usage in a client-side app using the [m3api](https://www.npmjs.com/package/m3api) library — by @lucaswerkmeister Note: The idea would be to add this support without introducing a build step — e.g., if we use a library to abstract the OAuth logic, it should be one that can be imported in a script tag from a CDN (or a vendored copy incuded the repo). Or we could use [htmx](https://htmx.org), which allows making network requests via declarative attributes in HTML tags, i.e. without writing javascript code.
AI Analysis
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be still under discussion. The issue was opened by waldyrious and has received 0 comments.
Add a comment
Comment form would go here