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] Column suggest can trigger when not inside jira codeblock fence #114

Open
1 of 5 tasks
nathonius opened this issue Jan 31, 2024 · 0 comments
Open
1 of 5 tasks
Assignees
Labels
bug Something isn't working

Comments

@nathonius
Copy link

nathonius commented Jan 31, 2024

Describe the bug
In certain, very specific situations, the column suggest will appear even when not in the jira codeblock.

To Reproduce
Steps to reproduce the behavior:

  1. Have a valid jira-search codeblock in a file.
  2. Somewhere after the jira codeblock, type columns:
  3. See the suggester appear outside the codeblock.

example file content:

```jira-search
type: TABLE
query: assignee = currentUser() AND status in ("Reopened", "Blocked", "To Do", "In Progress", "In Code Review", "Awaiting Validation") order by updated DESC
columns: KEY, SUMMARY, TYPE, UPDATED, STATUS
```

columns:

Expected behavior
The column suggester should not be visible when typing outside of the jira-search codeblock. Specifically I ran into this while developing another obsidian plugin, and it requires a fairly specific circumstance, so not a super high priority.

Plugin version and platform

  • Version: 1.56.0
  • Obsidian Windows
  • Obsidian Mac
  • Obsidian Linux
  • Obsidian Android
  • Obsidian iOS
@nathonius nathonius added the bug Something isn't working label Jan 31, 2024
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

2 participants