date removed from tparts 3 and 4

Author: mluukkai

src/content/10/en/part10a.md

@@ -90,20 +90,8 @@ Let us now run the script _npm start_
 >error:03000086:digital envelope routines::initialization
 >```
 >
-> <i>change the package.json as follows</i>
->
->```javascript
->{
->  // ...
->  "scripts": {
->    "start": "export SET NODE_OPTIONS=--openssl-legacy-provider && expo start", // highlight-line
->    "android": "expo start --android",
->    "ios": "expo start --ios",
->    "web": "expo start --web"
->  },
->  // ...
->}
->```
+> <i>the problem is most likely your Node version. In case of problems, switch to version _16.19.0_. See eg. [here](https://stackoverflow.com/questions/69692842/error-message-error0308010cdigital-envelope-routinesunsupported) for more.</i>
+
 
 The script starts the [Metro bundler](https://facebook.github.io/metro/) which is a JavaScript bundler for React Native. It can be described as the [Webpack](https://webpack.js.org/) of the React Native ecosystem. In addition to the Metro bundler, the Expo command-line interface should be open in the terminal window. The command-line interface has a useful set of commands for viewing the application logs and starting the application in an emulator or in Expo's mobile application. We will get to emulators and Expo's mobile application soon, but first, let's open our application.
   

src/content/10/en/part10b.md

@@ -41,14 +41,14 @@ const HelloWorld = props => {
 
 So we import the [Text](https://reactnative.dev/docs/text) component from React Native and replace the *div* element with a *Text* element. Many familiar DOM elements have their React Native "counterparts". Here are some examples picked from React Native's [Core Components documentation](https://reactnative.dev/docs/components-and-apis):
 
-- [Text](https://reactnative.dev/docs/text) component is <i>the only</i> React Native component that can have textual children. It is similar to for example the `<strong>` and the `<h1>` elements.
-- [View](https://reactnative.dev/docs/view) component is the basic user interface building block similar to the `<div>` element.
-- [TextInput](https://reactnative.dev/docs/textinput) component is a text field component similar to the `<input>` element.
-- [Pressable](https://reactnative.dev/docs/pressable) component is for capturing different press events. It is similar to for example the `<button>` element.
+- [Text](https://reactnative.dev/docs/text) component is <i>the only</i> React Native component that can have textual children. It is similar to for example the _&lt;strong&gt;_ and the _&lt;h1&gt;_ elements.
+- [View](https://reactnative.dev/docs/view) component is the basic user interface building block similar to the _&lt;div&gt;_ element.
+- [TextInput](https://reactnative.dev/docs/textinput) component is a text field component similar to the _&lt;input&gt;_ element.
+- [Pressable](https://reactnative.dev/docs/pressable) component is for capturing different press events. It is similar to for example the _&lt;button&gt;_ element.
 
 There are a few notable differences between core components and DOM elements. The first difference is that the <em>Text</em> component is <i>the only</i> React Native component that can have textual children. This means that you can't, for example, replace the <em>Text</em> component with the <em>View</em> component in the previous example.
 
-The second notable difference is related to the event handlers. While working with the DOM elements we are used to adding event handlers such as <em>onClick</em> to basically any element such as `<div>` and `<button>`. In React Native we have to carefully read the [API documentation](https://reactnative.dev/docs/components-and-apis) to know what event handlers (as well as other props) a component accepts. For example, the [Pressable](https://reactnative.dev/docs/pressable) component provides props for listening to different kinds of press events. We can for example use the component's [onPress](https://reactnative.dev/docs/pressable) prop for listening to press events:
+The second notable difference is related to the event handlers. While working with the DOM elements we are used to adding event handlers such as <em>onClick</em> to basically any element such as _&lt;div&gt;_ and _&lt;button&gt;_. In React Native we have to carefully read the [API documentation](https://reactnative.dev/docs/components-and-apis) to know what event handlers (as well as other props) a component accepts. For example, the [Pressable](https://reactnative.dev/docs/pressable) component provides props for listening to different kinds of press events. We can for example use the component's [onPress](https://reactnative.dev/docs/pressable) prop for listening to press events:
 
 ```javascript
 import { Text, Pressable, Alert } from 'react-native';

src/content/3/en/part3a.md

@@ -775,7 +775,6 @@ app.post('/api/notes', (request, response) => {
   const note = {
     content: body.content,
     important: body.important || false,
-    date: new Date(),
     id: generateId(),
   }
 

src/content/3/en/part3d.md

@@ -58,7 +58,6 @@ app.post('/api/notes', (request, response, next) => { // highlight-line
   const note = new Note({
     content: body.content,
     important: body.important || false,
-    date: new Date(),
   })
 
   note.save()

src/content/3/fi/osa3d.md

@@ -54,7 +54,6 @@ app.post('/api/notes', (request, response, next) => { // highlight-line
   const note = new Note({
     content: body.content,
     important: body.important || false,
-    date: new Date(),
   })
 
   note.save()

src/content/4/en/part4a.md

@@ -124,7 +124,6 @@ notesRouter.post('/', (request, response, next) => {
   const note = new Note({
     content: body.content,
     important: body.important || false,
-    date: new Date()
   })
 
   note.save()
@@ -292,10 +291,6 @@ const noteSchema = new mongoose.Schema({
     required: true,
     minlength: 5
   },
-  date: {
-    type: Date,
-    required: true,
-  },
   important: Boolean,
 })
 

src/content/4/fi/osa4a.md

@@ -120,7 +120,6 @@ notesRouter.post('/', (request, response, next) => {
   const note = new Note({
     content: body.content,
     important: body.important || false,
-    date: new Date(),
   })
 
   note.save()
@@ -285,7 +284,6 @@ const noteSchema = new mongoose.Schema({
     required: true,
     minlength: 5
   },
-  date: Date,
   important: Boolean,
 })
 

src/content/4/fi/osa4c.md

@@ -450,7 +450,7 @@ Huomaamme siis, että käyttäjällä on kaksi muistiinpanoa.
 
 Muistiinpanon luoneen käyttäjän id tulee näkyviin muistiinpanon yhteyteen:
 
-![Selain renderöi osoitteessa localhost:3001/api/notes taulukollisen JSON:eja joilla kentät content, important, date, id ja user, jonka arvo käyttäjäid](../../images/4/12e.png)
+![Selain renderöi osoitteessa localhost:3001/api/notes taulukollisen JSON:eja joilla kentät content, important, id ja user, jonka arvo käyttäjäid](../../images/4/12e.png)
 
 ### populate
 
@@ -503,7 +503,7 @@ notesRouter.get('/', async (request, response) => {
 
 Nyt käyttäjän tiedot tulevat muistiinpanon kenttään <i>user</i>:
 
-![Selain renderöi osoitteessa localhost:3001/api/notes taulukollisen JSON:eja joilla kentät content, important, date, id ja user. Kenttä user on olio jolla on kentät name, username ja id](../../images/4/15new.png)
+![Selain renderöi osoitteessa localhost:3001/api/notes taulukollisen JSON:eja joilla kentät content, important, id ja user. Kenttä user on olio jolla on kentät name, username ja id](../../images/4/15new.png)
 
 Korostetaan vielä, että tietokannan tasolla ei siis ole mitään määrittelyä sille, että esim. muistiinpanojen kenttään <i>user</i> talletetut id:t viittaavat <i>users</i>-kokoelman dokumentteihin.