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

[CURA-9859] Account for settingfunction value that evaluates to another settingfunction. #14121

Merged
merged 2 commits into from
Dec 30, 2022

Conversation

rburema
Copy link
Member

@rburema rburema commented Dec 23, 2022

Should fix #13675 ... at least our involvement with it. A bit worried about the other errors in that log :-/

@jellespijker jellespijker merged commit c03ed34 into main Dec 30, 2022
@jellespijker jellespijker deleted the CURA-9859_fix_ufp_settingfunction branch December 30, 2022 16:25
@fieldOfView
Copy link
Collaborator

Slightly off-topic: is the trailing underscore in arguments a new code-style standard?

@jellespijker
Copy link
Member

As far as I know, this wasn't a concise choice. It slipped past be during review.

On the topic of code-style, I think we should have an internal discussion somewhere this year. I think it would make sense to adhere to Python industry standards and I think multiple team mates agree with me on this.

@rburema
Copy link
Member Author

rburema commented Jan 17, 2023

Ah no sorry, that slipped by. I think I originally made it a local function and wanted to be sure it picked the right 'setting' variable during development.

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.

UFPWriter: SettingFunction is not JSON serializable
3 participants