material-ui: typography migration - suppress warning












0














I'm using material-ui in a react project and recently upgraded from a version < 3.2 to the latest version (currently 3.5). material-ui logs warnings regarding a deprecation in the Typography component:



 Warning: Material-UI: you are using the deprecated typography variants that will be removed in the next major release.

      Please read the migration guide under https://material-ui.com/style/typography#migration-to-typography-v2


I already migrated the variant prop in all Typography components I'm currently using according to the mapping table in the migration guide. I also tried setting the useNextVariants flag:



const theme = createMuiTheme({

  typography: {

    useNextVariants: true,

  },

});


However, material-ui keeps logging the warning. Is there anything else I need to do to remove usage of deprecated features? Is there a way to suppress the warning - in my running app as well as in jest snapshot tests?






material-ui







share|improve this question






















  • How does your component tree look likes? Looks like some of the material-ui components are not inside a MuiThemeProvider with that theme.
    – epsilon
    Nov 16 '18 at 13:28
















0














I'm using material-ui in a react project and recently upgraded from a version < 3.2 to the latest version (currently 3.5). material-ui logs warnings regarding a deprecation in the Typography component:



 Warning: Material-UI: you are using the deprecated typography variants that will be removed in the next major release.

      Please read the migration guide under https://material-ui.com/style/typography#migration-to-typography-v2


I already migrated the variant prop in all Typography components I'm currently using according to the mapping table in the migration guide. I also tried setting the useNextVariants flag:



const theme = createMuiTheme({

  typography: {

    useNextVariants: true,

  },

});


However, material-ui keeps logging the warning. Is there anything else I need to do to remove usage of deprecated features? Is there a way to suppress the warning - in my running app as well as in jest snapshot tests?






material-ui







share|improve this question






















  • How does your component tree look likes? Looks like some of the material-ui components are not inside a MuiThemeProvider with that theme.
    – epsilon
    Nov 16 '18 at 13:28














0












0








0







I'm using material-ui in a react project and recently upgraded from a version < 3.2 to the latest version (currently 3.5). material-ui logs warnings regarding a deprecation in the Typography component:



 Warning: Material-UI: you are using the deprecated typography variants that will be removed in the next major release.

      Please read the migration guide under https://material-ui.com/style/typography#migration-to-typography-v2


I already migrated the variant prop in all Typography components I'm currently using according to the mapping table in the migration guide. I also tried setting the useNextVariants flag:



const theme = createMuiTheme({

  typography: {

    useNextVariants: true,

  },

});


However, material-ui keeps logging the warning. Is there anything else I need to do to remove usage of deprecated features? Is there a way to suppress the warning - in my running app as well as in jest snapshot tests?






material-ui







share|improve this question













I'm using material-ui in a react project and recently upgraded from a version < 3.2 to the latest version (currently 3.5). material-ui logs warnings regarding a deprecation in the Typography component:



 Warning: Material-UI: you are using the deprecated typography variants that will be removed in the next major release.

      Please read the migration guide under https://material-ui.com/style/typography#migration-to-typography-v2


I already migrated the variant prop in all Typography components I'm currently using according to the mapping table in the migration guide. I also tried setting the useNextVariants flag:



const theme = createMuiTheme({

  typography: {

    useNextVariants: true,

  },

});


However, material-ui keeps logging the warning. Is there anything else I need to do to remove usage of deprecated features? Is there a way to suppress the warning - in my running app as well as in jest snapshot tests?






material-ui




material-ui






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 16 '18 at 13:21









wintermute

162




162












  • How does your component tree look likes? Looks like some of the material-ui components are not inside a MuiThemeProvider with that theme.
    – epsilon
    Nov 16 '18 at 13:28


















  • How does your component tree look likes? Looks like some of the material-ui components are not inside a MuiThemeProvider with that theme.
    – epsilon
    Nov 16 '18 at 13:28
















How does your component tree look likes? Looks like some of the material-ui components are not inside a MuiThemeProvider with that theme.
– epsilon
Nov 16 '18 at 13:28




How does your component tree look likes? Looks like some of the material-ui components are not inside a MuiThemeProvider with that theme.
– epsilon
Nov 16 '18 at 13:28

















active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53338753%2fmaterial-ui-typography-migration-suppress-warning%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53338753%2fmaterial-ui-typography-migration-suppress-warning%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

'app-layout' is not a known element: how to share Component with different Modules

Image
0 My application was working fine until I decided to go with lazy loading: So, my shared component looks like this: import { Component, Renderer2 } from '@angular/core'; export interface FormModel { captcha?: string; } @Component({ selector: 'app-layout', templateUrl: './app-layout.component.html', styleUrls: ['./app-layout.css'] }) export class FullLayoutComponent { } app-layout.component.ts I am using this component in my Another component say school-home.component.html like this: <app-layout> </app-layout> and it was working fine until I created a Module school-home.module.ts like this: import { NgModule } from '@angular/core'; import { CommonModule } from '@angular/common'; import { SchoolhomeRoutingModule ...
Read more

android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

Image
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box; } 0 This is a simple project showing cubes on Unity, exported to android project and imported on Android studio. On maifest file it showed following warning: Expecting <uses-feature android:name="android.software.leanback" android:required="false" /> tag I have no information about it. And also on default emptyview android project does not use/mention this feature. I know it is required by TV's and such but why its not added by default? Why is this? And Should I concern about it? android unity3d ...
Read more

WPF add header to Image with URL pettitions [duplicate]

Image
up vote 0 down vote favorite This question already has an answer here: Image source URI requiring authorization 3 answers Add header to all* HTTP requests on a machine 1 answer first of all sorry for my english. Recently I added some security in the backend of my project, and now I need to send a validation code(apiKey) inside the headers to retrieve the images. I have a problem with ALL images in my project that I had attached in my UI. For example, before I had: <Image Height="90" Source="{Binding Video.Thumbnail}"/> Now I need to change my code to create a CUSTOM petition add the apiKey in the header:...
Read more