refactor(apex): rearrange class for readability#29
Merged
Conversation
dschach
pushed a commit
that referenced
this pull request
Nov 7, 2023
🤖 I have created a release *beep* *boop* --- ## [1.3.2](v1.3.1...v1.3.2) (2023-11-07) ### Code Refactoring * **apex:** rearrange class for readability ([#29](#29)) ([e73a679](e73a679)) * rearrange modules to better order for parsing ([#30](#30)) ([b8e8a6f](b8e8a6f)) ### Styles * **monokai-sublime-apex:** update theme subscopes ([#27](#27)) ([837b79f](837b79f)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
refactor(params): simplify parameter usage, moving most to top-level
Of note: moving keyword lists to a separate file prevents the build/test process
refactor: moved some matchers to named objects for better readability
test: add illegal strings to prevent recognizing as other languages (clojure, gams, mathematica)
test: update expected markup after removing extra scope words
BEGIN_COMMIT_OVERRIDE
refactor(apex): rearrange class for readability
refactor(params): simplify parameter usage, moving most to top-level
refactor: moved some matchers to named objects for better readability
test: add illegal strings to prevent recognizing as other languages (clojure, gams, mathematica)
test: update expected markup after removing extra scope words
END_COMMIT_OVERRIDE