Files
tauri-plugins-workspace/.changes
TukanDev dc6d3321e5 feat(clipboard): Implement HTML and clear functionality (#977)
* Implement arboard HTML features (desktop only) and ability to trigger clipboard clear

Signed-off-by: TukanDev <contact@tukandev.com>

* Update readme of clipboard plugin

Signed-off-by: TukanDev <contact@tukandev.com>

* Update plugins/clipboard-manager/src/desktop.rs

Propagate error for clear as requested

Co-authored-by: Amr Bashir <amr.bashir2015@gmail.com>

* Update plugins/clipboard-manager/guest-js/index.ts

Change to camelCase as requested

Co-authored-by: Amr Bashir <amr.bashir2015@gmail.com>

* Update plugins/clipboard-manager/guest-js/index.ts

use camelCase here too

Co-authored-by: Amr Bashir <amr.bashir2015@gmail.com>

* Update README.md

Revert back as mentioned in HTML PR

* Update index.ts

After discussion  readHtml() is decided to be removed. Will follow and remove corresponding rust side function too.

* Strip all other existence of read_html out as determined in HTML support PR conversation

Signed-off-by: TukanDev <contact@tukandev.com>

* Apply requested changes v2

Signed-off-by: TukanDev <contact@tukandev.com>

* pnpm run build and cargo fmt

Signed-off-by: TukanDev <contact@tukandev.com>

* Update plugins/clipboard-manager/src/mobile.rs

fix ci calling

Co-authored-by: Amr Bashir <amr.bashir2015@gmail.com>

* mobile read_html omg....

Signed-off-by: TukanDev <contact@tukandev.com>

* Update plugins/clipboard-manager/src/mobile.rs

* pnpm format....

Signed-off-by: TukanDev <contact@tukandev.com>

* error on mobile as well

* clear on mobile

* change file

---------

Signed-off-by: TukanDev <contact@tukandev.com>
2024-02-25 19:46:12 +02:00
..
fmt
2024-02-19 17:17:22 -03:00
2024-02-21 13:34:10 -03:00
2024-02-22 22:20:16 -03:00
2023-04-25 17:31:33 +02:00
2024-02-21 13:29:09 -03:00

Changes

via https://github.com/jbolda/covector

As you create PRs and make changes that require a version bump, please add a new markdown file in this folder. You do not note the version number, but rather the type of bump that you expect: major, minor, or patch. The filename is not important, as long as it is a .md, but we recommend that it represents the overall change for organizational purposes.

When you select the version bump required, you do not need to consider dependencies. Only note the package with the actual change, and any packages that depend on that package will be bumped automatically in the process.

Use the following format:

---
"package-a": patch
"package-b": minor
---

Change summary goes here

Summaries do not have a specific character limit, but are text only. These summaries are used within the (future implementation of) changelogs. They will give context to the change and also point back to the original PR if more details and context are needed.

Changes will be designated as a major, minor or patch as further described in semver.

Given a version number MAJOR.MINOR.PATCH, increment the:

  • MAJOR version when you make incompatible API changes,
  • MINOR version when you add functionality in a backwards compatible manner, and
  • PATCH version when you make backwards compatible bug fixes.

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format, but will be discussed prior to usage (as extra steps will be necessary in consideration of merging and publishing).