nextcloud / nextcloud/workflow_script
Differentiate between postCreate and postWrite
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 89
- Forks
- 19
- Avg merge
- 6h 38m
- Merged PRs (30d)
- 3
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Feature request
Which Nextcloud Version are you currently using: 30.0.5
Is your feature request related to a problem? Please describe.
Right now creating a blank file, that is literally 0 bytes, triggers both postCreate and postWrite events.
This makes postCreate event less useful, because if you wanted to take action on both new and changed files, you could just select\write into your program both event types.
But if you want to take 1 type of action on newly created files, and another type of action on changed files, it is impossible to do so.
Describe the solution you'd like
Trigger postWrite only on changing an existing file
Describe alternatives you've considered
Is this a problem with Workflow Script or the underlying Nextcloud API? I can't tell. But this change would make automation with Nextcloud far more flexible.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how workflow_script handles the postCreate and postWrite events, then determine whether the behavior comes from the app or the underlying Nextcloud API. Done means creating a blank file triggers only postCreate, while writing to an existing file triggers postWrite.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100