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

Add support for String Property type and literal. #3490

Merged
merged 1 commit into from Aug 16, 2023

Conversation

mikeurbach
Copy link
Contributor

Contributor Checklist

  • Did you add Scaladoc to every public function/method?
  • Did you add at least one test demonstrating the PR?
  • Did you delete any extraneous printlns/debugging code?
  • Did you specify the type of improvement?
  • Did you add appropriate documentation in docs/src?
  • Did you request a desired merge strategy?
  • Did you add text to be included in the Release Notes for this change?

Type of Improvement

  • Feature (or new API)

Desired Merge Strategy

  • Squash: The PR will be squashed and merged (choose this if you have no preference).

Release Notes

Reviewer Checklist (only modified by reviewer)

  • Did you add the appropriate labels? (Select the most appropriate one based on the "Type of Improvement")
  • Did you mark the proper milestone (Bug fix: 3.5.x, 3.6.x, or 5.x depending on impact, API modification or big change: 6.0)?
  • Did you review?
  • Did you check whether all relevant Contributor checkboxes have been checked?
  • Did you do one of the following when ready to merge:
    • Squash: You/ the contributor Enable auto-merge (squash), clean up the commit message, and label with Please Merge.
    • Merge: Ensure that contributor has cleaned up their commit history, then merge with Create a merge commit.

This includes support for Property[String] and literals.
@mikeurbach mikeurbach added the Feature New feature, will be included in release notes label Aug 15, 2023
@mikeurbach mikeurbach added this to the 6.0 milestone Aug 15, 2023
Copy link
Member

@seldridge seldridge left a comment

Choose a reason for hiding this comment

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

LGTM

This is consistent with the previous approach for other properties. Thanks for factoring this work into multiple, small PRs.

@@ -110,6 +110,8 @@ object Serializer {
b ++= "SInt"; s(width); b ++= "(0h"; b ++= value.toString(16); b ++= ")"
case IntegerPropertyLiteral(value) =>
b ++= "Integer("; b ++= value.toString(10); b ++= ")"
case StringPropertyLiteral(value) =>
b ++= "String(\""; b ++= value; b ++= "\")"
Copy link
Member

Choose a reason for hiding this comment

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

I had thought there would be a cleaner way of expressing this. However, the alternative actually looks worse:

Suggested change
b ++= "String(\""; b ++= value; b ++= "\")"
b ++= """String(""""; b ++= value; b ++= """")"""

Let's keep this as-is. 😉

@jackkoenig jackkoenig merged commit 7a60422 into main Aug 16, 2023
18 checks passed
@jackkoenig jackkoenig deleted the mikeurbach/properties-string branch August 16, 2023 15:35
@sequencer
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature New feature, will be included in release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants