onepagezen / ob-frontend Goto Github PK

Form validations should be improved so that user knows which field field(s), specifically, are invalid. The current behavior is to throw a general error whenever ANY of the input fields are invalid upon form submit.

I was running gatsby build and saw this error in the terminal. Now sure what it means.

Missing onError handler for invocation 'building-schema', error was 'Error: Cannot create as TypeComposer the following value: Date.'. Stacktrace was 'Error: Cannot create as TypeComposer the following value: Date.
at SchemaComposer.createTempTC (C:\Users\jonah\Code\blog\node_modules\graphql-compose\lib\SchemaComposer.js:365:11)
at SchemaComposer.addAsComposer (C:\Users\jonah\Code\blog\node_modules\graphql-compose\lib\SchemaComposer.js:563:27)
at createSchemaComposer (C:\Users\jonah\Code\blog\node_modules\gatsby\src\schema\schema-composer.js:16:18)
at build (C:\Users\jonah\Code\blog\node_modules\gatsby\src\schema\index.js:104:26)
at buildSchema (C:\Users\jonah\Code\blog\node_modules\gatsby\src\services\build-schema.ts:19:3)'

Add link in meta to each post author, and when author name is clicked, should bring to author profile page.

gatsby-source-wordpress currently sets the limit of perPage comments to display at 100 (see gatsby-config.js). This will likely be fixed in gatsby-source-wordpress v4, and therefor the fix should be implemented after the migration to v4 has been completed.

Issue may have been resolved. Check existing application behavior.

'Loading' indicator appears when initially loading 'posts' page and results from the 'search' page. This same behavior should be added for when a user clicks the 'Next' and 'Previous' buttons using the pagination feature.

After deploying ob-frontend with
gatsby new blog https://github.com/onepagezen/ob-frontend
when I try to launch the project I get an error:
`"gatsby-source-wordpress" threw an error while running the sourceNodes lifecycle:

Cannot read property 'replace' of undefined

105 | touchNode
106 | } = actions;

107 | const normalizedBaseUrl = normalizeBaseUrl(baseUrl);
| ^
108 | _verbose = verboseOutput;
109 | _siteURL = ${protocol}://${normalizedBaseUrl};
110 | _useACF = useACF;

File: node_modules/gatsby-source-wordpress/gatsby-node.js:107:29`

This error is resolved by updating wordpress plugin to a newer one (I tried 4.0.0) but then the config file is incompatibe

Post card shows total number of comments for post, which is correct. However, posts don't display all comments (particularly those that are deeply nested), and therefor they should be removed from total count.

Current functionality allows for nested comments 2 layers deep. Additional functionality should allow for adding all comments (1, 2, 3, 4, 5, etc.) layers deep, and importing them into a 2-level nested comment format. This functionality is essential to allow for importing sites with many layers of nested (child) comments.

Anchor links can be implemented and work correctly within app. However, when freshly loading a page with anchor # attached to a post comment (each comment has a unique ID), page doesn't scroll to the comment location. It seems this functionality appears to work correctly for # Id's that are outside of the comment-list component.

Notes: Currently using Anchorate (https://www.npmjs.com/package/anchorate) for 'scroll-to-comment' functionality.