Skip to content

Conversation

@artembilan
Copy link
Member

Fixes #3735

The FeedEntryMessageSource adds an url to the provided metadataKey
making it incompatible when we provide a Resource-based configuration.

  • Remove adding of the url to the metadataKey making it rely only
    on the provided value
  • Remove internal Comparator for entries in favor of Comparator.comparing()
    feature
  • Improve some internal logic of the PropertiesPersistingMetadataStore
    when it emits a false warning: cannot create dirs, but they are present
  • Improve feed.adoc

Fixes spring-projects#3735

The `FeedEntryMessageSource` adds an url to the provided `metadataKey`
making it incompatible when we provide a `Resource`-based configuration.

* Remove adding of the url to the `metadataKey` making it rely only
on the provided value
* Remove internal `Comparator` for entries in favor of `Comparator.comparing()`
feature
* Improve some internal logic of the `PropertiesPersistingMetadataStore`
when it emits a false warning: cannot create dirs, but they are present
* Improve `feed.adoc`
Copy link
Contributor

@garyrussell garyrussell left a comment

Choose a reason for hiding this comment

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

LGTM, but there are some strange unrelated GraphQL errors in the action results.

@artembilan
Copy link
Member Author

Correct. See this first: #3756

@garyrussell garyrussell merged commit bba83c7 into spring-projects:main Mar 22, 2022
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.

Setting metadatakey on FeedEntryMessageSource using URL object is appending url to metadatakey but when Resource object is used, only metadatakey is set

2 participants