-
-
Notifications
You must be signed in to change notification settings - Fork 709
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
Documentation about FileProcessors #6374
Comments
Yes! |
Just checking :) What blockers are there to move this forward? |
None. |
At least for me. Lacking of time ;-) |
Few notes from me after working on some nette non-php file processors. {Type} can be some file type:
But that's obvious, right? :D |
@lulco Thanks. Sound good. Yes, for you and me it is obvious, but not for others, so you added already good points to start with from a beginners perspective. Would you be able to start a PR with some notes and i try to add or comment on it? |
I'm not very comfortable with writing documentation O:-) that's why I wrote those notes for you :) |
I am on it. |
* [TASK] Add documentation about FileProcessors Resolves: rectorphp/rector#6374 * [TASK] Change some things
rectorphp/rector-src@d553e84 [StaticTypeMapper] Register non-empty-array to ScalarStringToTypeMapper::SCALAR_NAME_BY_TYPE constant (#6374)
I would like to document, as promised, the new FileProcessors API.
@lulco:
Would you like to join me?
I would like to talk about the FileProcessors and the FileFormatters together because this seem somehow interconnected.
The text was updated successfully, but these errors were encountered: