# Way to post/pre process gcode through moonraker?

**URL:** <https://klipper.discourse.group/t/way-to-post-pre-process-gcode-through-moonraker/15058>\
**Category:** Developers\
**Created:** [March 19, 2024, 8:04am UTC](https://klipper.discourse.group/t/way-to-post-pre-process-gcode-through-moonraker/15058 "2024-03-19T08:04:43Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![theophile](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/theophile/32/31_2.png) [@theophile](https://klipper.discourse.group/u/theophile)\
**Post date:** [March 20, 2024, 6:23pm UTC](https://klipper.discourse.group/t/way-to-post-pre-process-gcode-through-moonraker/15058/9 "2024-03-20T18:23:01Z")

</div>

> [@coopergerman](#):
>
> i just moved most of the logic from the macro side to the `spoolman.py` file in moonraker components (i might create a spoolman branch somtime …)

I’d be interested to see what you’ve done here. While I was posting some of my macros/python/hacks above, it occurred to me that my whole approach really is little more than a patchwork of workarounds where a dedicated solution would be preferable. Spoolman already has a couple of Moonraker remote methods, maybe it would be better to build it out further to allow for this kind of functionality? Maybe projects like ERCF and SMuFF and Prusa’s MMU could benefit too. A while back @garethky posted [a thread about a system to allow Klipper to have more information about filament properties](https://klipper.discourse.group/t/assigning-a-filament-aka-thermal-preset-to-an-extruder/5849), and I wonder if those objectives could also be accomplished by extending Spoolman, even on single-material printers.

---

_[View the full topic](https://klipper.discourse.group/t/way-to-post-pre-process-gcode-through-moonraker/15058)._