Feature/general improvements #244
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gnikit
force-pushed
the
feature/general-improvements
branch
4 times, most recently
from
73a7707 to
5d53fd2
Compare
Closed
gnikit
force-pushed
the
feature/general-improvements
branch
from
3f7ce06 to
4b964b3
Compare
- The file structures have been updated to abide with the latest config syntax - Updated build commands in package.json - Deleted tasks.json.old
Regenerated npm and yarn .json files
The OpenMP regex did not allow for the OpenACC syntax scope to trigger. This has now been fixed and both should be displayed correctly. The only outstanding problem is that the unittest (.snap) does not trigger the right scopes, which means open acc/openmp are not tested thoroughly. I look into it
gnikit
force-pushed
the
feature/general-improvements
branch
from
4b964b3 to
4cd833b
Compare
Changes all fortls instances with global variable and makes pip install user based with upgrade.
Having preceding characters to ``` caused a problem in the hover result
- Adds support for all Fortran supported logical preprocessor operators - Adds support for arithmetic operators - Adds support for C++ preprocessor integers - Changes the syntax highlighting of preprocessor commands to use the `meta` scope which should result in consistent coloring between C++ and Fortran. A few things are not supported like macro function argument highlighting but I do not believe it is important for now
This was
linked to
issues
Oct 7, 2021
…n" or "procedure" #207 I have used non-fixed width ngative lookbehinds which should not be permitted in traditional Oniguruma regex. VSCode's implementation of the regex engine does not seem to care hence the solution
also extends the support for pfunit. Not sure if .pf and .fpp are considered to be fixed-form by default I don't think that is the case but fypp and pfunit use them so we default them to free-form
This is meant to make debugging syntax highlighting bugs easier to trace The unittests are also updated to contain the new scope names.
Labels were only captured at the start and end of a statement. Now we are also capturing them in between for if conditionals. The edits in the end in "named-control-constructs" are meant to correctly handle whitespaces which before they were placed as part of the group returned to the invalid.error.xxx A unittest has been added testing the conditionals with/out labels.
`stop` can now handle labels
Closed
Release a tag after token is uploaded
External extensions are enabled since we need the C++ extension for VSCode to launch without throwing an error. The tasks.json has been updated to call directly scripts from package.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR includes general improvements to the extension.
Details
yarn installgenerates the file).TODO:
publish.yml(VS_MARKETPLACE_TOKEN)Outstanding problems (currently wontfix)