Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Bundling Actions Together

Abierto
  • ¿Algo no está bien?
#461 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 4 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
python
Área
backend

Línea de trabajo

Comienza con AppBuilder y GraphBuilder y, después, sigue cómo se representan actions, transitions, subgraphs y MappedStates. Compara los puntos de entrada MultiAction y ActionChain propuestos con las API de builder existentes, incluida la alternativa with_subgraph. Se considera terminado cuando el proyecto tenga un diseño de action-graph reutilizable y acordado, incluido cualquier remapeo de entrada/salida y el comportamiento de validación.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area/core kind/feature priority/medium

Is your feature request related to a problem? Please describe.

@gamarin2 asks:

Hey! While working with class-based actions, I ended up creating state transitions that must logically be split in two separate actions, but where the second one must always be preceded by the first one.

In my case, it's a FormatSummarizer action that formats messages before transitioning to a Summarizer action. These two actions form what I would call an "action bundle": the second one can't be separated from the first one. For now, I have documented that requirement in my class docstring, but it would be nice to have it more strictly enforced. 

I'm sure there are various ways we could achieve this, but perhaps the easiest would be to add a property to the action class where you could specify preceding/following action classes. The AppBuilder would then fail to build if you haven't added the proper transitions.

@mdrideout also suggests:

I would say that I have a very large number of use cases for this, and creating an entire sub-graph for it is painful.

To piggyback on this, I also have a very large number of use cases for running actions with high concurrency, and have been creating sub-graphs simply for the purpose of running a single action for ~10 items. 
but I may be doing this as a workaround because I had a some issues trying to use MappedStates (?) with either pydantic or async.

Describe the solution you'd like
A way to have an action represent a graph.

class MultiAction:
    @abc.abstractmethod
    def get_graph() -> Graph:
        ...

class ActionChain(MultiAction):
    @abc.abstractmethod
    def get_actions() -> List[[Tuple[str, Union[Action, Callable]]]:
        ...

    def get_graph() -> Graph:
        named_actions = self.get_actions()
        action_names = [name for name, _ in named_actions]
        return GraphBuilder().with_actions(**dict(actions)).with_transitions(zip(action_name, action_names[1:]))

Describe alternatives you've considered
Could also have with_subgraph in builder, similar thing. This allows for packaging at the action level for reusability. Might also want the ability to remap inputs/outputs:

def state_maps() -> Tuple[dict, dict]:
    ....

Additional context
Add any other context or screenshots about the feature request here.

Lenguaje dominante
Python
Estrellas
2.6k
Forks
209
Merge medio
8 d 9 h
PR fusionados (30 d)
26

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de apache/burr

Todos los issues de apache/burr

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.