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

Auto-complete of aliases no more working after update to 18.7.9 #3065

Closed
myksto71 opened this issue Dec 21, 2018 · 6 comments
Closed

Auto-complete of aliases no more working after update to 18.7.9 #3065

myksto71 opened this issue Dec 21, 2018 · 6 comments
Assignees
Labels
feature Adding new functionality
Milestone

Comments

@myksto71
Copy link

After a update the last few weeks we see that autocomplete of aliases are no more working.
I noticed that a similar issue was opened more than 2 years ago: #372

What we have:

  • alias foo
    -- type hosts
    -- content 1.2.3.4

Now we add a new alias:

  • alias bar
    -- type hosts
    -- content: start typing foo, but no autocomplete happens (uppercase and lowercase).

Best Regards,
Michele.

@AdSchellevis
Copy link
Member

We seem to have missed the alias autocomplete function in the new alias system, with the new tokeniser it might be more difficult to integrate, we have to look into it.

I'll put it on the list of things todo, we should try to bring it back.

@AdSchellevis AdSchellevis self-assigned this Dec 22, 2018
@AdSchellevis AdSchellevis added the feature Adding new functionality label Dec 22, 2018
@myksto71
Copy link
Author

Thank you very much for your quick reply.
I really hope you can bring that function back and hope you will do it soon! ;)

Thanks you again and best regards.

Michele.

@AdSchellevis
Copy link
Member

This ab4e900 should fix the issue, although there is still a minor glitch in validation (ideally it shouldn't be possible to mix port and other types, but since it won't render defective configs I think it's good enough for now).

@myksto71
Copy link
Author

This ab4e900 should fix the issue, although there is still a minor glitch in validation (ideally it shouldn't be possible to mix port and other types, but since it won't render defective configs I think it's good enough for now).

Hi AdSchellevis.
Hi applied the patch and it seems to have solved to problem.
I have one question even thoght it may be silly: when any other update/upgrade will be applied we should apply the patch again or it will be included in the update/upgrade itself?

I really thank you very much for the job.

Best reagrds,
Michele.

@AdSchellevis
Copy link
Member

Hi Michele,

Thanks for confirming.
We'll try to add the patch to the next release, since the impact should be quite low.
Otherwise you should indeed patch again after upgrade, which you can easily do with our opnsense-patch utility.

Best regards,

Ad

@fichtner fichtner added this to the 19.1 milestone Dec 30, 2018
fichtner pushed a commit that referenced this issue Jan 4, 2019
@fichtner
Copy link
Member

fichtner commented Jan 4, 2019

Will be in 18.7.10.

@fichtner fichtner closed this as completed Jan 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Adding new functionality
Development

No branches or pull requests

3 participants