Skip to content
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

feat: allow plugin users to create a ClientUI #611

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

nicdumz
Copy link

@nicdumz nicdumz commented Jan 13, 2025

Greetings,

I would like to suggest an alternative to #591 which will allow unblocking the consumer getsops/sops#1641. (I'm interested in plugin support in sops so I can try out FIDO2 keys inside of Nix via sops-nix).

Instead of exposing all age internals into a separate package (which I presume isn't the best from a maintenance PoV), I move functions which need to be shared between plugin and main into two new internal private modules.

This lets me eventually expose NewClientUI() for consumers.

  • Move logging functions to internal/logger.
  • Move terminal related functions to internal/term
  • Expose a public plugin.NewClientUI()

Kudos to @brianmcgee for the original work.

@FiloSottile I'm happy to iterate on this code, let me know your constraints and I'll work with you.

HTH.

@nicdumz nicdumz changed the title feat: allow plugin users to create a ClientUI feat: allow plugin users to create a ClientUI Jan 13, 2025
This would allow `age` library users to create the needed inputs to interact with the `plugin` module.
@nicdumz
Copy link
Author

nicdumz commented Jan 14, 2025

And now with 💯 passing tests, sorry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant