Ashish Kumar (Ashfame)
@ashfame on WordPress.org and Slack
Interests
- Member Since: July 1st, 2007
- Location: Dubai, UAE
- Website: ashfame.com
- GitHub: ashfame
- Job Title: Software Engineer
- Employer: Automattic
Contribution History
Ashish Kumar (Ashfame)’s badges:- bbPress Contributor
- Core Contributor
- Meta Contributor
- Meta Team
- Plugin Developer
-
Committed [3275762] to Plugins SVN:
bump "Tested up to" version to 6.8 -
Committed [3218440] to Plugins SVN:
Update to version 2.0.0 from GitHub -
Closed pull request #86 on WordPress/try-wordpress:
API docs -
Closed pull request #125 on WordPress/try-wordpress:
Documentation for integrating and extending -
Closed pull request #126 on WordPress/try-wordpress:
Simulate data liberation via hook -
Closed pull request #128 on WordPress/try-wordpress:
Control preview automatically -
Closed issue #139 on the WordPress/try-wordpress repository:
Transform a Subject -
Closed issue #186 on the WordPress/try-wordpress repository:
DevEx: API for developers -
Closed issue #187 on the WordPress/try-wordpress repository:
Update documentation -
Merged pull request #196 into WordPress/try-wordpress:
Provide DevEx documentation -
Closed issue #194 on the WordPress/try-wordpress repository:
Build WordPress-y interface on top of our interface -
Merged pull request #195 into WordPress/try-wordpress:
DevEx API - WordPress-y version -
Closed issue #193 on the WordPress/try-wordpress repository:
Build API interface for developers to interact with -
Merged pull request #192 into WordPress/try-wordpress:
DevEx API -
Closed issue #185 on the WordPress/try-wordpress repository:
Switch our Transformer code to use registration of transformers approach -
Merged pull request #191 into WordPress/try-wordpress:
use TransformersRegistry approach for our own transformations -
Closed issue #184 on the WordPress/try-wordpress repository:
Registration of Transformers -
Merged pull request #190 into WordPress/try-wordpress:
Lay down foundation for utilizing TransformersRegistry class for transformers registration -
Submitted pull request #196 to WordPress/try-wordpress:
Provide DevEx documentation -
Submitted pull request #195 to WordPress/try-wordpress:
DevEx API - WordPress-y version -
Created issue #194 in the WordPress/try-wordpress repository:
Build WordPress-y interface on top of our interface -
Created issue #193 in the WordPress/try-wordpress repository:
Build API interface for developers to interact with -
Submitted pull request #192 to WordPress/try-wordpress:
DevEx API -
Submitted pull request #191 to WordPress/try-wordpress:
use TransformersRegistry approach for our own transformations -
Submitted pull request #190 to WordPress/try-wordpress:
Lay down foundation for utilizing TransformersRegistry class for transformers registration -
Created issue #187 in the WordPress/try-wordpress repository:
Update documentation -
Created issue #186 in the WordPress/try-wordpress repository:
DevEx: API for developers -
Created issue #185 in the WordPress/try-wordpress repository:
Switch our Transformer code to use registration of transformers approach -
Created issue #184 in the WordPress/try-wordpress repository:
Registration of Transformers -
Closed issue #143 on the WordPress/try-wordpress repository:
Compute the XPath of an element -
Merged pull request #180 into WordPress/try-wordpress:
define getElementXPath function to return full xpath -
Closed issue #182 on the WordPress/try-wordpress repository:
Updating the subject does not update the transformed post -
Pull request #183 merged into WordPress/try-wordpress:
Define custom hooks for transformer when liberated data is ready for transformation -
Submitted pull request #183 to WordPress/try-wordpress:
Define custom hooks for transformer when liberated data is ready for transformation -
Submitted pull request #180 to WordPress/try-wordpress:
define getElementXPath function to return full xpath -
Merged pull request #178 into WordPress/try-wordpress:
look for data in postmeta when transforming -
Submitted pull request #178 to WordPress/try-wordpress:
look for data in postmeta when transforming -
Closed issue #174 on the WordPress/try-wordpress repository:
Field names are still hardcoded in some places -
Merged pull request #177 into WordPress/try-wordpress:
Have all fields of subjects be dynamic on backend -
Submitted pull request #177 to WordPress/try-wordpress:
Have all fields of subjects be dynamic on backend -
Merged pull request #171 into WordPress/try-wordpress:
Ensure transformedId is an int -
Submitted pull request #171 to WordPress/try-wordpress:
Ensure transformedId is an int -
Closed issue #161 on the WordPress/try-wordpress repository:
Don't hardcode fields when getting or updating subject -
Merged pull request #170 into WordPress/try-wordpress:
Remove hardcoded fields -
Submitted pull request #170 to WordPress/try-wordpress:
Remove hardcoded fields -
Closed issue #152 on the WordPress/try-wordpress repository:
Backend API Design -
Closed issue #138 on the WordPress/try-wordpress repository:
Use Schemas to make backend generic -
Merged pull request #165 into WordPress/try-wordpress:
Schema transformation to drive API endpoints -
Submitted pull request #165 to WordPress/try-wordpress:
Schema transformation to drive API endpoints -
Closed pull request #153 on WordPress/try-wordpress:
Exploration: Existing API via schema
Developer
-
Chatrix
Active Installs: 30+