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

Evaluate IntrinsicFunctions from PayloadTemplate #236

Merged
merged 2 commits into from
Jul 2, 2024

Conversation

agrare
Copy link
Member

@agrare agrare commented Jul 2, 2024

No description provided.

@agrare agrare requested a review from Fryguy as a code owner July 2, 2024 16:58
@agrare agrare mentioned this pull request Jul 2, 2024
9 tasks
@Fryguy
Copy link
Member

Fryguy commented Jul 2, 2024

Overall, LGTM - minor comments above aside from simpler the predicate method contents.

@agrare agrare force-pushed the evaluate_intrinsic_functions branch 2 times, most recently from 8fe87e4 to 6f481cb Compare July 2, 2024 17:51
@Fryguy
Copy link
Member

Fryguy commented Jul 2, 2024

Gah I think this conflicted with the merge of #235

@agrare agrare force-pushed the evaluate_intrinsic_functions branch from 239ffcc to ff127e6 Compare July 2, 2024 18:00
@miq-bot
Copy link
Member

miq-bot commented Jul 2, 2024

Checked commits agrare/floe@10288f7~...ff127e6 with ruby 3.1.5, rubocop 1.56.3, haml-lint 0.51.0, and yamllint
7 files checked, 0 offenses detected
Everything looks fine. 👍

@Fryguy Fryguy merged commit da94e4f into ManageIQ:master Jul 2, 2024
5 checks passed
@Fryguy Fryguy added the enhancement New feature or request label Jul 2, 2024
Comment on lines 21 to 25
begin
tree = Parser.new.parse(payload)
rescue Parslet::ParseFailed => err
raise Floe::InvalidWorkflowError, err.message
end
Copy link
Member Author

Choose a reason for hiding this comment

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

@Fryguy maybe in a follow-up but what do you think about doing the Parser.new.parse in the initialize? It looks like it would always be the same for every invocation of value plus we like raising invalid workflow exception when building the Workflow instance not at runtime as much as possible

@agrare agrare deleted the evaluate_intrinsic_functions branch July 2, 2024 18:02
agrare added a commit that referenced this pull request Aug 1, 2024
Added
- Set Floe.logger.level if DEBUG env var set (#234)
- Add InstrinsicFunction foundation + States.Array, States.UUID (#194)
- Evaluate IntrinsicFunctions from PayloadTemplate (#236)
- Add more intrinsic functions (#242)
- Add State#cause_path, error_path (#249)
- Validate Catcher Next (#250)
- Add spec/supports (#248)

Fixed
- Handle non-hash input/output values (#214)
- Fix Input/Output handling for Pass, Choice, Succeed states (#225)
- Wrap Parslet::ParseFailed errors as Floe::InvalidWorkflowError (#235)
- Fix edge cases with States.Array (#237)
- Fix sporadic test failure with Wait state (#243)
- Fix invalid container names after normalizing (#252)

Changed
- Extract ErrorMatcherMixin from Catch and Retry (#186)
- Output should be JSON (#230)
- Normalize functions to all take arguments (#238)
- Pass full path name to State.new for better errors (#229)
- Validate that state machine input is valid JSON (#227)
- Move the Parslet parse into initialize so that invalid function definition will fail on workflow load (#245)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants