Feed Component
Allowing the user to view a post in the feed
Last updated
Allowing the user to view a post in the feed
Last updated
The second step to creating a miniapp is to define the feed component, which is what displays in the feed of Seam.
After running the ./seam-magic.sh
script in the quickstart, you'll be given a feed component that looks like this:
The job of the Feed Component is to read the data out of the model, and use it to render a post in the feed.
Just as you stored data in the composer component, in the feed component you'll need to get the strings you stored out. Getting data out of the model is as easy as:
Make sure that the key that you're looking at is the same as the one you used in your Composer Component.
Retrieving Numbers
To get numbers out of the model, you can use the Javascript function parseInt
, like so:
Retrieving Arrays
Once you've stored your array in the model using stringify
, you can get it back out again into an array by using JSON.parse
, like so:
It's important to check if the model data does have data in it to avoid crashing from the JSON parsing an undefined variable.
Then, once you have successfully retrieved your string data, you can render a component's UI. For example, here's a simple miniapp that just renders an image that it is given:
If your miniapp requires changing the data stored in a post after it has been posted to the feed (for example: the Poll Miniapp), use the update
function.
Not unlike the done function, update
is designed to take a single argument, your updated post data, of the following type: ({ [key: string]: string })
In the example of the Poll Miniapp, when a user votes on a poll, the new vote totals need to be stored and reflected across Seam. The update
function handles this by interacting with Seam's backend.
In the above example, after a Seam user casts their vote, the update
function is called with the updatedData containing the user's vote. The function call will update that post's data on Seam's backend.
Poll Miniapp postData before calling the update function:
After:
It is generally advised to update the local state before calling the update
function. This will provide immediate optimistic feedback to the user while the backend update is processed.