Comments (8)
dmkl
commented on July 3, 2024
1
Sorry, didn't have time yet. Found few issues with more strict checks for the output that can be fixed on our side. But didn't go through all failed specs yet.
from actor.
sunny
commented on July 3, 2024
Hi there! Thanks for bringing this up.
Release notes are in the CHANGELOG. The issues are most probably due to removing the OpenStruct dependency which has unintended consequences (#146).
Can you test your app against this PR? 🙏🏻 #148 (review)
from actor.
sunny
commented on July 3, 2024
This should be fixed up in version 3.8.1. Let us know if the issue persists 🙏🏻
from actor.
dmkl
commented on July 3, 2024
This fix didn't help. I will be able to check on my failing tests later and share the findings with you.
from actor.
sunny
commented on July 3, 2024
Maybe some more introspection methods on the end result that you depended on? I’ll reopen then. Thank you 🙏🏻
from actor.
sunny
commented on July 3, 2024
@dmkl Any new findings? 🙏🏻
from actor.
sunny
commented on July 3, 2024
FYI 3.9.0 has been released with #153, which could be related to your issues.
from actor.
sunny
commented on July 3, 2024
Closing this for now, feel free to answer or open a new issue if you encounter any more bugs.
from actor.
Related Issues (20)
- alias_input is documented but unavailable HOT 1
- What about improving the README about testing? HOT 1
- Get "TypeError: exception class/object expected" error when update from 3.1.3 to 3.6 HOT 2
- Question / feature request: hooks around call? HOT 6
- Missing note on stubbing ServiceActor::Result HOT 4
- Can't set an hash as a default value for an input HOT 1
- Keep Zeitwerk as a development dependency only HOT 2
- Consider removing `OpenStruct` usage HOT 2
- Consider dropping support for unmaintained Ruby releases HOT 1
- Misleading `ServiceActor::ArgumentError` message under specific circumstances HOT 8
- Make Actor result + pattern matching more pleasant HOT 1
- Actor's output names collision with `Object`'s instance methods HOT 2
- Using `Kernel.tap` and `Kernel.then` via `ServiceActor::Result` receiver HOT 1
- Is `DefaultCheck` obsolete? HOT 4
- Invoking undefined methods on `ServiceActor::Result` will lead to runtime errors in the next major release of Actor. HOT 29
- [Proposal] Default outputs via `output_of` actor class method HOT 3
- Breaking changes on ServiceActor::Result `failure?` after dropping `ostruct` ??? HOT 5
- Repeated `play` execution on 3.9.0 HOT 2
- Actor play continues to call subsequent actors/interactors when one of the interactors fail
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from actor.