Skip to content

Parse commented lines like an empty lines #1087

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

Closed
wants to merge 50 commits into from

Conversation

polo7
Copy link

@polo7 polo7 commented Jun 8, 2024

Fixes GH-277.
Idea: we parse a line and then evaluate despite it is commented. If there is a quote inside of comment then we get an exception "Missing a closing quote" (line 141 in spring-shell-core/src/main/java/org/springframework/shell/jline/ExtendedDefaultParser.java). To avoid this behavoir we should treat commented line like an empty. Then evaluate() from spring-shell-core/src/main/java/org/springframework/shell/Shell.java will take care of it with its "fail fast" on line 195.

jvalkeal added 2 commits June 20, 2024 17:06
@polo7
Copy link
Author

polo7 commented Jun 24, 2024

Hello, @jvalkeal ! I didn't want to disturb you but it seems you are the only active official in this repo. Could you please guide me with my further steps? I guess I need your approval here.

github-actions bot and others added 25 commits June 25, 2024 12:08
- New Screen.Writer has new text method taking
  AttributedString instead of just String
- Fixes spring-projects#1110
- Can change item text
- Can position items by priority(true left, false right)
  and primary(sort for draw attempt)
- Fixes spring-projects#1112
- Add unicode handling in flow components in
  AbstractTextComponent which allows StringInput
  to process unicode given from jline.
- This add basic non-english character support
  for input.
- Fixes spring-projects#1115
- Add note for interactive mode
- Fixes spring-projects#1108
- Fix an issue where unknown option is wrongly
  lexed as an argument if it's later than an known
  valid option.
- Essentially if `arg1` is only valid option
  `--arg1 value1 --arg2 value2` would not complain
  about `arg2`.
- Fixes spring-projects#1120
- Remove javadoc related tasks from root project
- Add aggregated javadoc task to spring-shell-docs
- Various antora version updates
- Bundle javadoc via collector into antora build
- Remove refs to distZip in workflows
- Relates spring-projects#1132
- i.e. disabling jar will make local publish fail
- Relates spring-projects#1132
- Starter for jline ffm terminal provider
- Build changes for compiling with gradle toolchains
  defaulting to jdk22
- spring-shell-sample-ffm which compiles with jdk22
- ci workflow setups jdk 17/22
- Relates spring-projects#1131
- Change toolchain to get configured immediately instead
  after project evaluation which somehow caused i.e.
  vscode not detect correct project jdk in use.
- Relates spring-projects#1131
- Essentially this is a workflow acting as a placeholder
  for doing further native development as it's easier
  to have on in a main branch.
- Should eventually grow into one user can run manually
  for ffm development if it's required to build something
  on a gh platform.
- To prepare jdk17+ code, don't fail if there's
  more recent javadoc format.
- Relates spring-projects#1131
- Prepare build so that we can use JUnit tags and
  define shellIncludeTags/shellExcludeTags from
  command line to override settings.
- Needed for some of a new planned tests which
  would not work without full build.
- Relates spring-projects#1131
Update to Commons-IO 2.18.0
Corneil du Plessis and others added 14 commits December 10, 2024 13:53

Verified

This commit was signed with the committer’s verified signature.
fmbenhassine Mahmoud Ben Hassine

Verified

This commit was signed with the committer’s verified signature.
fmbenhassine Mahmoud Ben Hassine

Verified

This commit was signed with the committer’s verified signature.
fmbenhassine Mahmoud Ben Hassine

Verified

This commit was signed with the committer’s verified signature.
fmbenhassine Mahmoud Ben Hassine

Verified

This commit was signed with the committer’s verified signature.
fmbenhassine Mahmoud Ben Hassine
Spring Boot 3.5 updated JUnit Jupiter from v5.11 to v5.12.
With this new version, the junit-platform-launcher dependency
must be declared explicitly.
fix type

Signed-off-by: benson-yeh <[email protected]>

Verified

This commit was signed with the committer’s verified signature.
fmbenhassine Mahmoud Ben Hassine

Verified

This commit was signed with the committer’s verified signature.
fmbenhassine Mahmoud Ben Hassine

Verified

This commit was signed with the committer’s verified signature.
fmbenhassine Mahmoud Ben Hassine
@fmbenhassine
Copy link
Contributor

Thank you for the PR! LGTM 👍

Can you please rebase it on the latest main branch and add a test for that case? It should then be good to merge for the upcoming 3.4.1 release.

Thank you upfront.

@fmbenhassine fmbenhassine added this to the 3.4.1 milestone Apr 25, 2025
@fmbenhassine fmbenhassine changed the title gh-277: parse commented line like an empty line Parse commented lines like an empty lines Apr 25, 2025
codespearhead and others added 4 commits April 25, 2025 11:21
- Bump node-pty from 0.11.0-beta19 to 1.0.0
- Bump xterm-headless from 4.18.0 to 5.5.0
- Rename xterm-headless to @xterm/headless as per https://www.npmjs.com/package/xterm-headless
- Unpin Python 3.11 in e2e test by reverting commit spring-projects@8097f1e because it's no longer necessary as explained in spring-projects#909 (comment)

- Fixes spring-projects#909
- Fixes spring-projects#921
@polo7
Copy link
Author

polo7 commented Apr 28, 2025

Thank you for the PR! LGTM 👍

Can you please rebase it on the latest main branch and add a test for that case? It should then be good to merge for the upcoming 3.4.1 release.

Thank you upfront.

@fmbenhassine I've rebased my branch on top of main and added unit tests to cover different cases and different implementations of Parser. Let me know if there is anything else I need to do to go further.

@fmbenhassine
Copy link
Contributor

Thank you for the update! However I don't see the PR rebased on the latest main with those 48 commits and 109 files changed (not related to this PR). The PR should have a single commit with the change set you want to introduce. I don't know how I can help here but try to rebase your PR again. Otherwise you can open another one if it's easier for you.

@fmbenhassine fmbenhassine added the status/need-feedback Calling participant to provide feedback label Apr 28, 2025
@polo7
Copy link
Author

polo7 commented Apr 29, 2025

@fmbenhassine I went through PR creation once again and it shows me PR is already opened with changes I've made.
Maybe I should close this one and create PR one more time, I don't know. It seems like a bug here.

@polo7
Copy link
Author

polo7 commented May 1, 2025

@fmbenhassine this is my another PR instead of this one: #1168

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/need-feedback Calling participant to provide feedback
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Quotes Should Not Be Recognized In Comments
6 participants