| import React from 'react'; | |
| import { render, fireEvent } from 'react-native-testing-library'; | |
| import { _EditPlanDetails as EditPlanDetails } from '../Settings/EditPlanDetails'; | |
| // Scrollviews are bugged in the current Expo/RN release and won't render in tests https://github.com/expo/expo/issues/2806#issuecomment-465373231 | |
| jest.mock('ScrollView', () => require.requireMock('ScrollViewMock')); | |
| describe('EditPlanDetails', () => { | |
| const props = { | |
| subscription: { |
| <head> | |
| <!-- this will run --> | |
| <style nonce='1234'> | |
| .a { | |
| color: red; | |
| } | |
| </style> | |
| <!-- this won't run --> | |
| <style> |
| /** | |
| * @typedef {Object} ClassifyProps | |
| * @property {React.ElementType} [as] - Element to render | |
| * @property {import('clsx').ClassValue} [className] - Composable classnames passed to clsx | |
| */ | |
| /** | |
| * @param {ClassifyProps} props | |
| */ | |
| function Classify({ as: El = "div", ...props }) { |
I created this gist in order to help myself and others keep track of tips and tricks in order to make Gatsby v2 play nicely with Internet Explorer 10 and 11.
This is experience based. Please share your experiences when you have a solution to a problem.
If you suspect that an es6-based module is breaking your app, then try to add gatsby-plugin-compile-es6-packages and include the package as one of the modules.
| <%@ Register Tagprefix="SharePointWebControls" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> | |
| <SharePointWebControls:ScriptLink language="javascript" name="reputation.js" OnDemand="false" LoadAfterUI="true" runat="server" Localizable="false" /> |
| // ---------------------------------------------------------------------- | |
| // Smart wrapper around Next.js <Link> | |
| // | |
| // This is to improve the default handling of Next.js dynamic links which | |
| // requires both `href` and `as` props. | |
| // This improvement enables the following usage: | |
| // | |
| // <Link page="/users/[id]" params={{ id: user.id }}>{user.name}</Link> | |
| // | |
| // <Link page="/blog/[...slug]" params={{ slug: ['coffee', 'frenchpress'] }}>View Here</Link> |
| // put this in a file where your service worker used to live, like yourdomain.com/service-worker.js. You can find out this path in the SW dev tools of your browser | |
| self.addEventListener('install', (e) => { | |
| console.log('[Service Worker] Installing Service Worker ...', e); | |
| self.skipWaiting(); | |
| }); | |
| self.addEventListener('activate', (e) => { | |
| console.log('[ServiceWorker] Activate'); | |
| self.registration |
| #!/bin/bash | |
| # | |
| # Credits to fuckbecauseican5 from https://www.reddit.com/r/hackintosh/comments/4s561a/macos_sierra_16a238m_install_success_and_guide/ | |
| # Adapted to work with the official image available into Mac App Store | |
| # | |
| # Enjoy! | |
| hdiutil attach /Applications/Install\ macOS\ Sierra.app/Contents/SharedSupport/InstallESD.dmg -noverify -nobrowse -mountpoint /Volumes/install_app | |
| hdiutil create -o /tmp/Sierra.cdr -size 7316m -layout SPUD -fs HFS+J | |
| hdiutil attach /tmp/Sierra.cdr.dmg -noverify -nobrowse -mountpoint /Volumes/install_build |
| git filter-branch --env-filter 'export GIT_COMMITTER_DATE="$GIT_AUTHOR_DATE"' |
