Paulo Pinto
@psrpinto on WordPress.org, @Paulo Pinto on Slack
- Member Since: May 3rd, 2021
- Location: Lisbon, Portugal
- GitHub: psrpinto
- Job Title: Software Engineer
- Employer: Automattic
Contribution History
Paulo Pinto’s badges:- Core Contributor
- Meta Contributor
- Meta Team
- Plugin Developer
- Translation Contributor
-
Closed pull request #2053 on WordPress/wordpress-playground:
Make it easy to test-publish packages -
Closed pull request #124 on WordPress/try-wordpress:
Document how to contribute site definitions -
Merged pull request #189 into WordPress/try-wordpress:
Guarantee that src/plugin/schema.json is up-to-date -
Submitted pull request #189 to WordPress/try-wordpress:
Guarantee that src/plugin/schema.json is up-to-date -
Closed issue #176 on the WordPress/try-wordpress repository:
Test that everything works when a schema is created or modified -
Merged pull request #188 into WordPress/try-wordpress:
Temporarily use pg.ashfame.com -
Closed issue #159 on the WordPress/try-wordpress repository:
Blueprints are broken when the name of a field in the schema... -
Submitted pull request #188 to WordPress/try-wordpress:
Temporarily use pg.ashfame.com -
Merged pull request #183 into WordPress/try-wordpress:
Define custom hooks for transformer when liberated data is ready for transformation -
Created issue #182 in the WordPress/try-wordpress repository:
Updating the subject does not update the transformed post -
Merged pull request #179 into WordPress/try-wordpress:
Log playground requests -
Created issue #181 in the WordPress/try-wordpress repository:
Show requests to Playground in the network tab of the browser's developer... -
Submitted pull request #179 to WordPress/try-wordpress:
Log playground requests -
Closed issue #162 on the WordPress/try-wordpress repository:
Schema: `required` attribute might be unnecessary -
Merged pull request #175 into WordPress/try-wordpress:
Remove required property from fields -
Created issue #176 in the WordPress/try-wordpress repository:
Test that everything works when a schema is created or modified -
Submitted pull request #175 to WordPress/try-wordpress:
Remove required property from fields -
Closed issue #172 on the WordPress/try-wordpress repository:
Can't find subject by source URL when calling the API -
Merged pull request #173 into WordPress/try-wordpress:
Correctly call API when searching by source URL -
Closed issue #137 on the WordPress/try-wordpress repository:
Use Schemas to make frontend generic -
Created issue #174 in the WordPress/try-wordpress repository:
Field names are still hardcoded in some places -
Submitted pull request #173 to WordPress/try-wordpress:
Correctly call API when searching by source URL -
Created issue #172 in the WordPress/try-wordpress repository:
Can't find subject by source URL when calling the API -
Closed issue #157 on the WordPress/try-wordpress repository:
Display field description in the UI -
Merged pull request #169 into WordPress/try-wordpress:
Display field description -
Created issue #68090 in the WordPress/gutenberg repository:
Error in @wordpress/components Storybook -
Closed issue #167 on the WordPress/try-wordpress repository:
Don't hardcode subject types -
Merged pull request #168 into WordPress/try-wordpress:
Don't hardcode subject type -
Closed issue #155 on the WordPress/try-wordpress repository:
Dynamically display import buttons for all registered subjects -
Submitted pull request #169 to WordPress/try-wordpress:
Display field description -
Submitted pull request #168 to WordPress/try-wordpress:
Don't hardcode subject type -
Created issue #167 in the WordPress/try-wordpress repository:
Don't hardcode subject types -
Submitted pull request #166 to WordPress/try-wordpress:
Display import buttons for all registered subjects -
Closed issue #156 on the WordPress/try-wordpress repository:
SubjectsApi should automatically figure out which endpoints to call -
Merged pull request #160 into WordPress/try-wordpress:
Make SubjectsApi automatically figure out which endpoints to call -
Merged pull request #154 into WordPress/try-wordpress:
Use Schema to make frontend generic (part 1) -
Created issue #161 in the WordPress/try-wordpress repository:
Don't hardcode fields when getting or updating subject -
Submitted pull request #160 to WordPress/try-wordpress:
Make SubjectsApi automatically figure out which endpoints to call -
Created issue #159 in the WordPress/try-wordpress repository:
Blueprints are broken when the name of a field in the schema... -
Created issue #158 in the WordPress/try-wordpress repository:
Handle the plural form of subject titles -
Created issue #157 in the WordPress/try-wordpress repository:
Display field description in the UI -
Created issue #156 in the WordPress/try-wordpress repository:
SubjectsApi should automatically figure out which endpoints to call -
Created issue #155 in the WordPress/try-wordpress repository:
Dynamically display import buttons for all registered subjects -
Submitted pull request #154 to WordPress/try-wordpress:
Use Schema to make frontend generic (part 1) -
Closed issue #135 on the WordPress/try-wordpress repository:
Load a Schema using JavaScript -
Submitted pull request #151 to WordPress/try-wordpress:
Function to load schema from javascript -
Merged pull request #148 into WordPress/try-wordpress:
Call schema validation from build process -
Submitted pull request #148 to WordPress/try-wordpress:
Call schema validation from build process -
Closed issue #134 on the WordPress/try-wordpress repository:
Define the structure of a Schema with a json-schema.org -
Merged pull request #145 into WordPress/try-wordpress:
Add JSON Schema and individual schema files
Developer
-
Chatrix
Active Installs: 30+
-
OpenID Connect Server
Active Installs: 60+
Contributor
-
Tours
Active Installs: 20+