Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 4 years ago.
Improve this question
I am new to react-native, I have created createMaterialTopTabNavigation -- i.e, Login & Signup.
In my LoginScreen there is another screen ForgotPassword IDK how can I navigate to ForgotPassword screen from LoginScreen while I have only created one navigation i.e, CreateMaterialTopTabNavigation
You can use createStackNavigator as main navigation and createMaterialTopTabNavigation as first config that will execute.
try this,
...//your old navigators
const stack = createStackNavigator({
tab:AppTabNavigator,
forgotPassword:...// your forgot password screen
})
and then if you're using react-navigation#3.x then you need to wrap this stack in appContainer and export it.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 9 months ago.
Improve this question
I am using vue3-sfc-loader. I can get it working, but I am unable to use other components (also loaded from the same plugin) inside of a component. I have gone through documentation and searched whole day, but I am not able to figure out what am I missing.
I found the answer. Answering for anyone needing it.
You can use import statement with relative path to your another component inside script tag of your SFC.
Also, you need to include the component in list of components you want to use.
import currency from './currency.vue';
export default ({
props: {
...
},
components: {
'currency': currency
},
setup() {
},
...
Although someone in discussions on githhub mentions that you can use import statements.. it doesn't work.
Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 2 years ago.
Improve this question
Whenever I try to click on the button it doesn't add any records. But when I put on the input field #keyup.enter="addusers" Then it's working when I press enter. I want it to work with Add button. Can someone give me advice.
.row
input(type='text', v-model='newUser')
input(type='text', v-model='newMail')
button.btn.btn-primary(type='button' #onclick="addUsers") Add
.col-lg-12.text-left(v-for="user in users")
p {{ user.name}}- {{user.email}}
addUsers() {
axios.post('https://jsonplaceholder.typicode.com/users', {
name: this.newUser,
email: this.newMail
})
.then(({data}) => {
this.users.push(data);
});
the click event should be written #click instead of #onclick
button.btn.btn-primary(type='button' #click="addUsers") Add
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
If you open any CodeSandbox default Vue template, or just vue-cli default template like this
import Vue from "vue";
import App from "./App.vue";
Vue.config.productionTip = false;
new Vue({
render: h => h(App)
}).$mount("#app");
It will have an additional <Root /> element.
And it breaks everything that writes this.$root.
Why is this happening?
Is there any way to solve this?
If you add some data to the root Vue instance - you will see in DevTools that it is different from the data in your App component:
import Vue from "vue";
import App from "./App.vue";
Vue.config.productionTip = false;
new Vue({
data:
{
someTest: 123,
},
render: h => h(App)
}).$mount("#app");
What is happening has been happening for years. You can not solve it because this is by design and can not work without it.
If you want to access App instead of the root instance - then you will have to use this.$root.$children[0]
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 3 years ago.
Improve this question
i have two component, component A check Internet access and change connection state.
Component A
now i want pass "connection" state to B component and setstate there with a
a new state...
Component B
now
Since network state is used throughout the app, it's better to warp it at the root level.
And use Context to pass the props.
Here NetworkStatusContext is used to pass network state to child components.
<NetworkStatusContext.Provider value={isConnected}>
<App />
</NetworkStatusContext.Provider>
Then you can get the network state at any component.
<NetworkStatusContext.Consumer>
{isConnected =>
(!isConnected ? <ErrorMessageComponent/>: <SomeComponent/>
)}
</NetworkStatusContext.Consumer>
For above question!
Passing props from Component A -> B
render(){
return(
<ComponentB
connection={this.state.connection}
/>
);
}
In component B you can access props as:
render(){
const{connection}=this.props;
.....
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 4 years ago.
Improve this question
i have created 3 pages, first page is navigating to second page and second page is navigating to 3rd page, how ever when i click back button it is navigating to previous page but its not giving last history intead of its reloading the page,
This is normal as the previous component's instance is destroyed. You can console.log in each lifecycle hook to see which hooks are called when a route is entered and exited.
To prevent this behaviour and cache your route's component you can wrap the <router-view> inside <keep-alive>
<keep-alive>
<router-view></router-view>
</keep-alive>
You can even pass include and exclude props on <keep-alive> to manage which component to or not be cached