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

[BUG] Failed to parsetemplate #496

Open
kapral18 opened this issue Dec 23, 2024 · 6 comments
Open

[BUG] Failed to parsetemplate #496

kapral18 opened this issue Dec 23, 2024 · 6 comments
Labels
bug Something isn't working

Comments

@kapral18
Copy link

kapral18 commented Dec 23, 2024

Describe the bug
Getting a parsetemplate error when trying to invoke a custom command

To Reproduce
Apply config with this keybinding:

keybindings:
  issues:
    - key: e
      command: >
        tmux new-window -c {{.RepoPath}} "nvim -c \":silent Octo issue edit {{.IssueNumber}}\""

Steps to reproduce the behavior:

  1. Go to issues view
  2. Hit e
  3. See error

I tried all combinations of quotes single double and in between, result is the same

Expected behavior
No error and command executed

Screenshots
image

Desktop (please complete the following information):

  • OS: Mac 15.2
@kapral18 kapral18 added the bug Something isn't working label Dec 23, 2024
@MaikuMori
Copy link

I just fixed something related. In my case, I didn't configure RepoPaths correctly in the config.yaml. See if checkout works by pressing "shift+c", if it doesn't then your RepoPaths are wrong.

The error message seems to be very misleading.

@kapral18
Copy link
Author

@MaikuMori why do I need to add repopaths in config? Shouldn't it lookup the repo path dynamically of an individual issue or PR selected in the dash?

@kapral18
Copy link
Author

ok I think I got it, I need to provide repoPath like

repoPaths: 
    :owner/:repo: ~/code/github.com/:owner/:repo

And indeed the original error is gone, thanks

@MaikuMori
Copy link

@dlvhdr I would still consider this as an open bug. The error message is very confusing in this case and doesn't explain how to fix the issue properly.

@dlvhdr
Copy link
Owner

dlvhdr commented Jan 12, 2025

Agree

@dlvhdr dlvhdr reopened this Jan 12, 2025
@kapral18
Copy link
Author

Agree as well thanks @MaikuMori. For the context @dlvhdr I was using repoPaths: {} in my config when this was happening.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants
@MaikuMori @kapral18 @dlvhdr and others