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

Expose a TypeMarker factory to wrap an arbitrary Type #2221

Merged
merged 2 commits into from
Mar 22, 2024

Conversation

carterkozak
Copy link
Contributor

This mirrors a change we've just introduced to conjure-undertow here: palantir/conjure-java#2264

Dialogue takes advantage of this new factory method in ConjureBodySerDe to avoid holding class references in serializer caches, which introduced some friction in our dns-polling lifecycle management. I haven't reverted the change to specify weakKeys in the caches, however the keys should never be freed unless classes are unloaded (e.g. plugins).

==COMMIT_MSG==
Expose a TypeMarker factory to wrap an arbitrary Type
==COMMIT_MSG==

This mirrors a change we've just introduced to conjure-undertow
here: palantir/conjure-java#2264

Dialogue takes advantage of this new factory method in ConjureBodySerDe
to avoid holding class references in serializer caches, which
introduced some friction in our dns-polling lifecycle management.
I haven't reverted the change to specify `weakKeys` in the caches,
however the keys should never be freed unless classes are unloaded
(e.g. plugins).
@changelog-app
Copy link

changelog-app bot commented Mar 22, 2024

Generate changelog in changelog/@unreleased

What do the change types mean?
  • feature: A new feature of the service.
  • improvement: An incremental improvement in the functionality or operation of the service.
  • fix: Remedies the incorrect behaviour of a component of the service in a backwards-compatible way.
  • break: Has the potential to break consumers of this service's API, inclusive of both Palantir services
    and external consumers of the service's API (e.g. customer-written software or integrations).
  • deprecation: Advertises the intention to remove service functionality without any change to the
    operation of the service itself.
  • manualTask: Requires the possibility of manual intervention (running a script, eyeballing configuration,
    performing database surgery, ...) at the time of upgrade for it to succeed.
  • migration: A fully automatic upgrade migration task with no engineer input required.

Note: only one type should be chosen.

How are new versions calculated?
  • ❗The break and manual task changelog types will result in a major release!
  • 🐛 The fix changelog type will result in a minor release in most cases, and a patch release version for patch branches. This behaviour is configurable in autorelease.
  • ✨ All others will result in a minor version release.

Type

  • Feature
  • Improvement
  • Fix
  • Break
  • Deprecation
  • Manual task
  • Migration

Description

Expose a TypeMarker factory to wrap an arbitrary Type

Check the box to generate changelog(s)

  • Generate changelog entry

}

@Override
@SuppressWarnings("unchecked")
public <T> Deserializer<T> deserializer(TypeMarker<T> token) {
return (Deserializer<T>) deserializers.get(token);
return (Deserializer<T>) deserializers.get(token.getType());
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Changes to this file would also make sense in a separate PR

@bulldozer-bot bulldozer-bot bot merged commit ce016a7 into develop Mar 22, 2024
6 checks passed
@bulldozer-bot bulldozer-bot bot deleted the ckozak/TypeMarkerFactory branch March 22, 2024 17:56
@svc-autorelease
Copy link
Collaborator

Released 3.125.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants