feat(core): Update config with more concrete copy paths#123
Merged
Conversation
Saloed
force-pushed
the
DanielELog/new_config
branch
from
e1db07a to
af9afb4
Compare
Reconstruct DanielELog/new_config's config reorganization (commit e1db07a, "Update config with more concrete copy paths") on top of current main. The original single commit cannot be rebased directly: main and the branch both restructured the same files. This regenerates the branch's curated per-library layout against main instead: - Adopt the branch's 149 per-library/per-package config files (self-described via `library:` headers), relocated to core/opentaint-config/java-config/ config/java-config/, replacing main's monolithic config.yaml + jmod.yaml + jar-split/. - Apply main's map-storage field migration to the adopted content: for the 14 map-like classes main migrated (java.util.Map, javax.script.Bindings, Guava Cache/Multimap/Table, Gson JsonObject, commons-collections4, Spring, ...), rewrite `<rule-storage>` -> `MapValue`. Branch curation is preserved; main's rename applies only to functions the branch kept. - Take main's StringBuilder/StringBuffer/AbstractStringBuilder taint rules from #230 ("chained StringBuilder.append taint loss"), which rewrote those rules coupled to engine changes. The branch's older curation of the same functions is dropped in favour of #230; its rules land in stdlib/java-lang-stringbuilder.yaml, and the branch's versions are stripped from stdlib/java-lang.yaml. - Keep accumulated-fields.yaml at the module resource root, matching the branch. ConfigLoader walks only the /java-config subtree, so it is not deserialized as a taint config (main has no `fields` schema yet); it lies dormant until its consumer feature lands. Verified: ConfigLoader.getConfig() loads all files under real kaml; every file uses only main-supported keys at rule and copy level; no stale map-storage tokens remain; the StringBuilder-family rule set equals main #230 exactly.
Saloed
force-pushed
the
DanielELog/new_config
branch
from
af6cb69 to
ad32d82
Compare
Saloed
approved these changes
Jul 1, 2026
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
2 participants
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.
https://github.com/seqra/opentaint-test/actions/runs/28547743370