Danger
Training exercise.
- The concept of the feature is great.
- Works well with React pages
- In the docs it's saying that "getServerProps function receives two parameters". But there are actually described 3 parameters.

- Inserting
imgmarkdoc tag in editor produces opening and closing tag (though it is unary tag). - It is hard to debug what is inside
$pagePropsin markdown pages. We decided to create a tsx page instead and renamed old markdown page. Since we had active and renamed markdown page in file editor - Webview rendered it and got stuck on that url. Full Webview restart did not help to switch to valid url. - When making changes to react page inside editor Webview reacts on every change and reloads too often and page ends up with javascript errors.
- It is hard to debug what data comes from calls to third-party services inside
.props.ts. - We were not able to use api functions endpoint inside
.props.tsfile. - Working with
$pagePropsin markdown file is very unstable. Sometimes it works, sometimes it crashes, sometimes it does not return any data. Relatead to MD files. - If
$pagePropshas image link, it is not possible to render image in md file. We tried three ways:![](), image html tag (<img />) and image markdoc tag{% img %}. - If
$pagePropshas type integer or float, it breaks md file.