Skip to content

Conversation

@andclt
Copy link

@andclt andclt commented Feb 3, 2025

Notes

Jira issue: MSHADE-156

Add the option to skip relocating string literals. Currently this is not possible and the only available solution is to create a "fake" relocation pattern to prevent such behavior, example.
This change adds a new property skipStringLiteral which still relocates the prefix instances but not the string literals.

Testing

mvn clean verify

Results:
[INFO] Tests run: 72, Failures: 0, Errors: 0, Skipped: 0

Following this checklist to help us incorporate your
contribution quickly and easily:

  • Make sure there is a JIRA issue filed
    for the change (usually before you start working on it). Trivial changes like typos do not
    require a JIRA issue. Your pull request should address just this issue, without
    pulling in other changes.
  • Each commit in the pull request should have a meaningful subject line and body.
  • Format the pull request title like [MSHADE-XXX] - Fixes bug in ApproximateQuantiles,
    where you replace MSHADE-XXX with the appropriate JIRA issue. Best practice
    is to use the JIRA issue title in the pull request title and in the first line of the
    commit message.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Run mvn clean verify to make sure basic checks pass. A more thorough check will
    be performed on your pull request automatically.
  • You have run the integration tests successfully (mvn -Prun-its clean verify).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

@Goooler
Copy link
Member

Goooler commented Apr 16, 2025

Seems this also addresses MSHADE-153.

@jira-importer
Copy link

Resolve #518

1 similar comment
@jira-importer
Copy link

Resolve #518

@elharo
Copy link
Contributor

elharo commented Sep 11, 2025

can you merge with master?

@elharo elharo changed the title [MSHADE-156] - Allow non relocating string literals [MSHADE-156] Allow non relocating string literals Sep 25, 2025
Copy link
Contributor

@elharo elharo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This feels like it needs some additions to the docs somewhere. Adding a property without documenting it is unlikely to help folks.

* @param entityName entity name to be mapped
* @param mapPaths map "slashy" names like paths or internal Java class names, e.g. {@code com/acme/Foo}?
* @param mapPackages map "dotty" names like qualified Java class or package names, e.g. {@code com.acme.Foo}?
* @param mapLiterals map string literals, e.g. {@code "com.acme.Foo"}?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

extra space before map


@Test
public void testShaderWithoutStringLiterals() throws Exception {
Shader s = newShader();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s -> shader

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

Successfully merging this pull request may close these issues.

4 participants