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

/INCLUDE Path in Local Development Case Sensitivity Inconsistent #307

Open
SJLennon opened this issue Mar 22, 2024 · 1 comment
Open

/INCLUDE Path in Local Development Case Sensitivity Inconsistent #307

SJLennon opened this issue Mar 22, 2024 · 1 comment

Comments

@SJLennon
Copy link
Contributor

Save us time! Click 'Report an Issue' from the Help and Support panel inside of VS Code after you have connected to a system.
Would like to, but deliberately not connected to a system to ensure no side effects.
Version: 1.87.1 (user setup)
Commit: 1e790d77f81672c49be070e04474901747115651
Date: 2024-03-06T00:21:36.258Z
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Windows_NT x64 10.0.19045

Code for IBM i v2.8.0

Describe the bug
The documentation says that for local development in /COPY and /INCLUDE statements the path is case sensitive. (https://codefori.github.io/docs/extensions/rpgle/faq/). I missed this when converting some code to a local repository and while tidying up I noticed what appear to be an inconsistency.

For demonstration purposes, I have three /INCLUDE statements, thus, all for the same file:

1) /INCLUDE ../Copy_Mbrs/aidbytes.rpgle
2) /INCLUDE ../Copy_Mbrs/AIDBYTES.RPGLE
3) /INCLUDE ../COPY_MBRS/AIDBYTES.RPGLE

My directory structure looks like this:
image
image

Hovering over 1) shows as not found because the case does not match:
image
Hovering over 2) correctly shows as found because the case matches:
image
Hovering over 3) also shows as found, yet the case does not match:
image

I intend to match the case. But I find this inconsistency curious.

@SJLennon
Copy link
Contributor Author

While doing more tidy up on other code, it seems like the problem might be with caching of the path.

@worksofliam worksofliam transferred this issue from codefori/vscode-ibmi Mar 25, 2024
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

No branches or pull requests

1 participant