https://cypress.io logo
Join Discord
Powered by
# vue
  • l
    import {i18n} from './plugins/i18n'
  • r
    Ok I'll try it, but, that workaround would be in cypress docs?, other Vue developers will have the same issue
  • l
    I think this goes in the main.js file. It may not work, but I think that will solve the issue for _t
  • r
    Hi Bryan, Did you check the example repo? https://github.com/xanxuz/vue-cypress-ct
  • l
    I did.
  • l
    I'm looking over this issue as a whole, so I may have missed some details.
  • l
    import i18n from './translations';
  • l
    This might work in the App.vue file instead. I'd try both.
  • l
    (Separately)
  • r
    Ok, I tried to import the i18n file in the cypress/support file (the one with "Vue.use(Vuei18n)" ) to check if that way could work but it didn't. The i18 file has this:
  • b
    @User the instance of Vue used in mount is not the one exxposed in import Vue
  • b
    This avoids having to do some painful teardown after each it
  • b
    But it's more complicated than it seems to use plugins
  • l
    Sorry. What about line 4 in main.js?
  • b
    This will have no effect on the mounted component since cypress mount uses a localVue instance
  • b
    So this line will install i18n on the globally exposed Vue instance... but mount is not using this instance.
  • b
    This is why you have to create the mounti18n function
  • u
    Maybe?
    Copy code
    js
import { i18n } from '<your_path>/i18n';
...
mount(Component, {
  ...,
  i18,
  ...
})
  • b
    You should even probably create a mount that sets up all your plugins as needed
  • l
    What about the export from vue-cypress-ct/src/plugins/i18n.js
  • l
    This is a 'new' instance instead of the actual component.
  • r
    So the only way for now to affect all tests is creating a helper function of mount?, I thought that the support file was for that case.
  • b
  • b
    The support file is only loading stuff outside of Vue
  • b
    if you want to influence the instance of Vue, you have to do it using a wrapper function
  • l
    Yep.
  • r
    If you put that in a helper function as @User mentioned yes, but doing that per each test file is not viable.
  • b
    It has big advantages if you ask me
  • l
    Yeah. Looking at it a little deeper this makes sense.
  • b
    It makes setup more explicit (plus if you are using typescript you can use F12 to follow what is happening)
1...171819...37Latest