You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I've started using your plugin and it looks very promissing!
I have come across a problem that I think (and hope) would be easy to fix:
I'm using the plugin in a dynamic way, which means I build dynamically the configs attribute:
contentReplace(
configs: [
variablesReplaceConfig( configs: variablesReplacersList,
This means I'm creating a list of objects of type VariablesReplaceItemConfig which are NOT serializable, and here is the problem:
Because it isn't serializable, I'm forced to apply the plugin inside a function that is annotated with "@NonCPS", but such functions are NOT supposed to utilize pipeline steps...
Would it be possible to make the VariablesReplaceItemConfig class serializable?
B.T.W - there is a mistake in the plugin page in the buttom:
variableReplace(
configs: [
variablesReplaceConfig(...
variableReplace should be contentReplace.
The text was updated successfully, but these errors were encountered:
Hi,
I've started using your plugin and it looks very promissing!
I have come across a problem that I think (and hope) would be easy to fix:
I'm using the plugin in a dynamic way, which means I build dynamically the configs attribute:
contentReplace(
configs: [
variablesReplaceConfig(
configs: variablesReplacersList,
This means I'm creating a list of objects of type VariablesReplaceItemConfig which are NOT serializable, and here is the problem:
Because it isn't serializable, I'm forced to apply the plugin inside a function that is annotated with "@NonCPS", but such functions are NOT supposed to utilize pipeline steps...
Would it be possible to make the VariablesReplaceItemConfig class serializable?
B.T.W - there is a mistake in the plugin page in the buttom:
variableReplace(
configs: [
variablesReplaceConfig(...
variableReplace should be contentReplace.
The text was updated successfully, but these errors were encountered: