Skip to content

Only use JSON-native types with sidekiq#461

Draft
adamruzicka wants to merge 2 commits intoDynflow:masterfrom
adamruzicka:sidekiq-json
Draft

Only use JSON-native types with sidekiq#461
adamruzicka wants to merge 2 commits intoDynflow:masterfrom
adamruzicka:sidekiq-json

Conversation

@adamruzicka
Copy link
Contributor

No description provided.

@adamruzicka
Copy link
Contributor Author

Let's see what the tests think

This has two effects - it casts the input to only contain JSON-native
objects and removes amiguity on the receiving end. With the previous
implementation, we couldn't reliably distinguish whether what we're
accessing was previously dumped into a json by dynflow or if it is a
user-provided json-encoded string.
@ofedoren
Copy link

Probably needs a rebase, although the tests are green. Can we run this PR against some real scenarios? I mean, to run these changes against foreman-tasks and/or Katello?..

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.

2 participants