Skip to content

Conversation

@sesquialtera87
Copy link
Contributor

Referring to #607, the following changes has been made:

  • text surrounded by square brackets ([some text]) is no longer recognized as an INI section when placed in a property value context
  • values enclosed in single and double quotes are highlighted as strings (TokenTypes.LITERAL_STRING_DOUBLE_QUOTE)

@codecov
Copy link

codecov bot commented Jun 2, 2025

Codecov Report

Attention: Patch coverage is 86.71875% with 17 lines in your changes missing coverage. Please review.

Project coverage is 80.53%. Comparing base (da8e1d6) to head (07ec5cc).
Report is 6 commits behind head on master.

Files with missing lines Patch % Lines
...g/fife/ui/rsyntaxtextarea/modes/IniTokenMaker.java 86.71% 15 Missing and 2 partials ⚠️
Additional details and impacted files
@@            Coverage Diff            @@
##             master     #622   +/-   ##
=========================================
  Coverage     80.53%   80.53%           
- Complexity     7865     7879   +14     
=========================================
  Files           180      180           
  Lines         30438    30481   +43     
  Branches       3925     3928    +3     
=========================================
+ Hits          24513    24548   +35     
- Misses         4256     4265    +9     
+ Partials       1669     1668    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

reset(text, 0, text.count, 0);
yylex();
} catch (IOException e) {
throw new RuntimeException(e);
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will crash some apps if there is a bug in the highlighting. While RSTA's current behavior of silently returning not text isn't great, I'd rather keep the current behavior consistent across all TokenMakers.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This and the previous issue have been fixed: the semicolon is restored as comment marker and no exception is thrown during unexpected lexical errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants