Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add YAML import/export for Text Expander snippets

Open
  • Is something wrong?
#625 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
kotlin, yaml
Domain
mobile

Research direction

Start by reading the existing application-data import/export flow and how LeanType represents Text Expander snippets; the issue does not name specific files. Work out how snippet fields map to the requested YAML format, including compatibility with Espanso. Done means snippets can be exported to and imported from standalone YAML files; the optional read-only YAML view is an additional convenience.

Written by the indexing model from the issue text.

Description

enhancement
Feature request

It would be useful to have standalone import and export for Text Expander snippets using YAML/YML.

Currently, LeanType can export its application data, but there is no way to import or export Text Expander snippets separately. The application-specific data format also makes the snippets difficult to use outside LeanType.

I would like to be able to:

  • Export Text Expander snippets as a .yaml/.yml file.
  • Import snippets from a YAML file.
  • Use a standard, portable format that can be used with other text-expansion applications, such as Espanso.

For example:

matches:
  - trigger: ":email"
    label: "Email"
    replace: "[email protected]

As a small additional convenience, it could also be useful to have a read-only view showing all snippets in their YAML format, similar to how Expanda displays them. Editing the YAML inside LeanType is not necessary; I could edit the exported file elsewhere and import it again.
The main goal is simply to make Text Expander data portable instead of being locked into LeanType's application-specific format.

I've added a reference image from expanda for how the snippets can ne showed in their yamal format as read only.

Image
Dominant language
Kotlin
Stars
1k
Forks
59
Avg merge
13h 21m
Merged PRs (30d)
48

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from LeanBitLab/LeanType

All issues in LeanBitLab/LeanType

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.