[PR #49] [MERGED] fix unexpected token BlockEnd (}) #59

Closed
opened 2026-02-28 01:20:44 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/tufanbarisyildirim/gonginx/pull/49
Author: @Nobilta
Created: 7/5/2024
Status: Merged
Merged: 10/13/2024
Merged by: @tufanbarisyildirim

Base: masterHead: fix-unexpected-BlockEnd


📝 Commits (2)

  • 11f4b23 fix unexpected token BlockEnd (})
  • a54cac6 fix detecting end of the block

📊 Changes

1 file changed (+3 additions, -0 deletions)

View changed files

📝 parser/parser.go (+3 -0)

📄 Description

fix this issue https://github.com/tufanbarisyildirim/gonginx/issues/48
When the parser encounters a keyword type and enters parseStatement, during the process of parsing parameters until the end, if the end is directly a BlockEnd, it cannot match and correctly exit the parseStatement function. Therefore, when looping to match until exiting parseStatement, it is necessary to first check if the next token is BlockEnd, and if so, return and exit directly.
@tufanbarisyildirim


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/tufanbarisyildirim/gonginx/pull/49 **Author:** [@Nobilta](https://github.com/Nobilta) **Created:** 7/5/2024 **Status:** ✅ Merged **Merged:** 10/13/2024 **Merged by:** [@tufanbarisyildirim](https://github.com/tufanbarisyildirim) **Base:** `master` ← **Head:** `fix-unexpected-BlockEnd` --- ### 📝 Commits (2) - [`11f4b23`](https://github.com/tufanbarisyildirim/gonginx/commit/11f4b231bbbe52d3eff7b2daa130edc6915e204c) fix unexpected token BlockEnd (}) - [`a54cac6`](https://github.com/tufanbarisyildirim/gonginx/commit/a54cac63f593080eeb089a63a11ec126840c88a3) fix detecting end of the block ### 📊 Changes **1 file changed** (+3 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `parser/parser.go` (+3 -0) </details> ### 📄 Description fix this issue https://github.com/tufanbarisyildirim/gonginx/issues/48 When the parser encounters a keyword type and enters parseStatement, during the process of parsing parameters until the end, if the end is directly a BlockEnd, it cannot match and correctly exit the parseStatement function. Therefore, when looping to match until exiting parseStatement, it is necessary to first check if the next token is BlockEnd, and if so, return and exit directly. @tufanbarisyildirim --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-02-28 01:20:44 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/gonginx#59
No description provided.