now_playing | : musical_note : Output the currently scrobbling song | Navigation library

Edit your views:

Concept

A great way to poll APIs is to schedule requests in javascript then wait a certain amount of time (no more than 10-30 seconds) for the server to hold the request to see if the song changes then return the result. If the result is found earlier than 10-30 seconds, the server returns it early. The client sees the request as in progress, and can receive it in the entire window the server has it as long as the request does not time out (exceeds 30+ seconds or so). You can also just simply request the url every few seconds to check, but that uses a lot of system resources.

API Code

You can add it as a parameter to your enum case like: case popular(queryParameters: [String: Any])

You can create Router class that has buildRequest(_:Endpoint), and here you can get the queryParameters and add it to the url witch will contain page and limit or any other query parameters.

you can also add another parameter for bodyParameters if the request HTTPMethod is POST and you need to send data in the body.

There are couple of issues with using JSDOM there, especially the way you are using it.

Firstly the website in question does not have any markup for the DOM element with the class name movie-list-body as you retrieve it using Axios

On further inspection I realised they are using a jQuery AJAX call to retrieve all the links and images from a JSON file.

Following is the script they are using to do so.

By removing import ffmpeg the disconnecting problem no longer occurs. All of the commands work with no problems whatsoever.

Using ctx.message.guild.voice_client.disconnect() does not destroy the player object created by music.create_player(ctx, ffmpeg_error_betterfix=True).

This means that when you try to play something after the bot has disconnected and connected to a voice channel, it will attempt to use the old player object which is no longer valid, even if the bot connects to the same voice channel.

Checking the source code for DiscordUtils.Music, there are two methods that you can use to destroy player, either player.disable() or player.delete().

If you want to wait in the splash screen, you will need to make that request in the splash screen.

When you have a successful response, you then navigate and pass the data through args/intent extras, assuming this is a different fragment/activity.

Then, when you are setting creating the list adapter you just need to pass this list through the constructor and set wire everything up, like you probably already have.

Hope it helps, but let me know if this wasn't clear enough!

There is no way to eliminate the risk of structural changes to the source content.

You can take some steps to minimize the likelihood that you forget to change your code - for example, by removing the need for hard-coded +13 and -1. But there can be other reasons for your code to fail, beyond that.

It's probably more important to make it extremely obvious when your code does fail.

Consider the following sample (which does not use Cheerio, for simplicity):

If I understand the expected behavior correctly, you're trying to update the movies state in movies.js from the search.js.

You are updating two different states of two different components that have no relationship with themselves and that is why nothing is happening on submit.

What you'll need is a parent component (for example home.js) that holds search and movies component as children and holds the movies state. The child components should use and update the parent's movie state.