eyn

const MaterialUIIconResolver = {
  apply(resolver) {
    resolver.plugin("module", function resolve(request, callback) {
      if (/material-ui-icons/.test(request.context.issuer)) {
        if (request.request === "material-ui/SvgIcon") {
          const newRequest = Object.assign({}, request, {
            request: "material-ui-next/SvgIcon"
          });
          return this.doResolve(
            "resolve",

eyn

/* eslint-disable no-undef */
/* eslint-disable @typescript-eslint/no-var-requires */
const { writeFileSync } = require("fs");
const { compile } = require("json-schema-to-typescript");
const { mapValues, upperFirst, camelCase } = require("lodash");
const prettier = require("prettier");
const StoryblokClient = require("storyblok-js-client");

const interfaceName = (name) => upperFirst(camelCase(name));

eyn

ACCESS CONTROL POLICY

INTRODUCTION AND PURPOSE

This document defines the Access Control Policy for Flex Legal Ltd. The policy applies to all staff (including temporary, contract, third party and agency staff) working for, or on behalf of, the organisation.

The objective of this policy is to prevent unauthorised access to the Company's information systems and networks. The policy will describe how access controls are applied by the organisation, covering all stages in the life-cycle of user access, from the initial registration process of new users to the final deregistration of users who no longer require access to information systems and services.

Provision of Authorization and Access to Company Systems

The Company is divided into the following classifications:

Flex Sales, Bookings & Onboarding Team

eyn

Keybase proof

I hereby claim:

• I am eyn on github.
• I am eyn (https://keybase.io/eyn) on keybase.
• I have a public key ASCrXjPwlG4P4iaKb67Y2E_9YNeY6efAGVKEpLDsSy8LQwo

To claim this, I am signing this object:

eyn

Upgrade Notes

Material-UI was started 3 years ago. The ecosystem has evolved a lot since then, we have also learned a lot. @nathanmarks started an ambitious task, rebuilding Material-UI from the ground-up taking advantage of this knowledge to address long-standing issues.

There are major breaking changes between v0.1x and v1. There is often no direct mapping from the v0.1x API to the v1 API so moving from v0.1x to v1 can require quite extensive changes. Luckily these don't all need to be done at one time and you can run v0.1x side by side with v1 while you move between versions.

Side by Side Installation

To install v1 alongside v0.1x will will create a new package material-ui-next which aliases to the v1 release and leave material-ui pointing to the 0.1x release. We can then import components as follows: