open-weather | lightweight jQuery plugin used to display | REST library

It looks like openweathermap API has a timezone tag as well - seconds as offset from UTC. Maybe something like this works?

You can't change the route or use the Vue-router from inside the Electron main process, as you also can't access the Electron Menu from inside any Vue component for activating / deactivate submenus according to the login state (another doubt I had posted and answered myself).

Electron Menus should always be managed at the Electron main process.

Vue routes should always be managed at the Electron renderer process - from inside Vue components.

So, as the events are generated on layers different from the ones where they should be treated, in both cases, just notify each other layer, through IPC messages, that you want that thing to change and it will be changed there, at the proper layer.

In the case of changing the Menu, the login / logout Vuex state is checked inside the Vue components, then the component sends an IPC call to the main process and the submenus are activated or deactivated there. See this solution on the link:
How to activate / deactivate an Electron.js submenu from inside a Vue.js Component according to a specific Vuex state?

Another similar solution is the one for this post problem, but the other way around:

For changing the routes, instead of using win.loadURL() or win.loadFile() at the main process side, one should send an IPC call to the renderer side, in this case to the App.vue component, using win!.webContents.send("changeRouteTo", "/"), for example. The "changeRouteTo" is a custom channel name and the "/" is the path to which the router, from inside the Vue component, at the renderer side, will change the route to - for the "/" it's the "Home" route. For changing to the "Login" route, the path would be "/login", and so on... according to the router.ts config. At the renderer side, in this case at the App.vue component, it is set an IPC renderer listener for the "changeRouteTo" channel or event, and, each time it receives a route change request from the main process, then this.$router.push() is used, from inside this component, to change the route to that correspondent route.

This should work both for development and non development environments, when using npm run electron:serve to run the project, as for the final build execution, after npm run electron:build is called and a bundle is created.

Hope this solution is useful to others.

See the full final project here, it's a pretty nice sample app:
https://github.com/danielpm1982/open-weather-client

OK, nobody knew this one, so I managed to work around it myself... and I'm sharing the solution to help others.

I actually could not find a way to get or manage the Electron Menu at the renderer process, from within the Vue components, so I let it to be updated at the main process itself, where I have access to all Electron components easily.

Finally, I managed to fix issue by conditionally setting the props for components in render() function like this:

You can't reach data from outside of async function. You need to do your process in subscribe.

I'm not sure why you are using rapidapi here, but if you simply want to fetch data from openweathermap, you need to do the following:

• Sign up to get unique API key (free plan exist)
• Provide the key as part of your URL, like:

http://api.openweathermap.org/data/2.5/forecast?id=524901&APPID={APIKEY}, When APIKEY is your unique API key

Also make sure you do not use the API key from the demos provided by open weather map, as it will result with errors when used from domain other than openweathermap, And tha if you're using a free plan, you're limited to maxium of 60 request per minute.

Check out the docs about how to get started with openweathermap.

When I call {{weather$}} it shows on the screen: Country: object Objects..

You are printing an observable not the data.

If you want to print observable data in the html, you can use async pipe.

To print the entire data object do:

Looks like you're rendering your component before the data is fetched. Try giving defaults to the data passed to the component, or check if data exists before rendering. Something like:

Unfortunately, here on SO nobody came up with a solution, yet a colleague (he doesn't have an SO account) made a pull request with the migration fixes. It works perfectly, and I decided to post the correct answer here as well.

If you're interested in how these improvements look inside the actual code, you're welcome to visit the original open source project page on GitHub: Open Weather App

This is the new adapter: