Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Fix: #59 support the ability to get the line number where the nginx directive is located #60

Merged

Conversation

sharelinux
Copy link
Contributor

Support the ability to get the line number where the nginx directive is located.

This PR is for Issue: #59, which supports parsing of nginx directives to get the line number in the configuration file where the directive is located.

I hope it will be merged.

@tufanbarisyildirim
Copy link
Owner

thanks for the contribution @sharelinux I love such handy additions!

@tufanbarisyildirim tufanbarisyildirim merged commit 78982de into tufanbarisyildirim:master Dec 18, 2024
1 check passed
@sharelinux
Copy link
Contributor Author

I found that the warehouse small version number change a little slow ah, in fact, many features may last about a year to hit the tag, suggest 1 ~ 2 weeks can be sent some changes in the small version.

When go get gets the code, actually go mod will automatically pull the code repository of the larger tag, but you need to use v2.0.1 this kind, you need to tag with v prefix.

I'm also happy to contribute code and use open source to contribute to open source.

Thanks again for the merger.

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

Successfully merging this pull request may close these issues.

2 participants