@iamproperty/components 2.9.0 → 3.1.0

package/README.md

@@ -1,137 +1,16 @@
-# Getting started
+# Vue 3 + TypeScript + Vite
 
-## Using the component library or assets
+This template should help get you started developing with Vue 3 and TypeScript in Vite. The template uses Vue 3 `<script setup>` SFCs, check out the [script setup docs](https://v3.vuejs.org/api/sfc-script-setup.html#sfc-script-setup) to learn more.
 
-### Install
-```
-npm install @iamproperty/components --save
-```
+## Recommended IDE Setup
 
-### Usage
+- [VS Code](https://code.visualstudio.com/) + [Volar](https://marketplace.visualstudio.com/items?itemName=Vue.volar)
 
-#### Static assets
+## Type Support For `.vue` Imports in TS
 
-The assets folder can be used independently from the Vue components so that they can be used with other frameworks. With the compiled files available to use out of the box alongside the source files that can be configured. 
+Since TypeScript cannot handle type information for `.vue` imports, they are shimmed to be a generic Vue component type by default. In most cases this is fine if you don't really care about component prop types outside of templates. However, if you wish to get actual prop types in `.vue` imports (for example to get props validation when using manual `h(...)` calls), you can enable Volar's Take Over mode by following these steps:
 
-```
-<link href="./node_modules/@iamproperty/components/assets/css/style.min.css" as="style" />
-<script src="./node_modules/@iamproperty/components/assets/js/scripts.bundle.min.js"></script>
-```
+1. Run `Extensions: Show Built-in Extensions` from VS Code's command palette, look for `TypeScript and JavaScript Language Features`, then right click and select `Disable (Workspace)`. By default, Take Over mode will enable itself if the default TypeScript extension is disabled.
+2. Reload the VS Code window by running `Developer: Reload Window` from the command palette.
 
-##### Sass files
-```
-@import './node_modules/@iamproperty/components/assets/sass/_func.scss';
-@import './node_modules/@iamproperty/components/assets/sass/_corefiles_.scss';
-```
-##### JS modules
-```
-import navbar from @iamproperty/components/assets/js/modules/navbar.js
-```
-
-
-#### Vue application
-
-```
-import '@iamproperty/components/assets/css/core.min.css'
-import '@iamproperty/components/dist/components.css'
-
-import * as iamkey from '@iamproperty/components'
-for (const [key, value] of Object.entries(iamkey)) {
-  Vue.component(key, value)
-}
-```
-
-Components then can be used as described in the design system documentation.
-
-```
-<Header title="Page title" image="../../assets/image.jpeg"><p>Page description</p></Header>
-```
-
-#### NUXT
-
-To use the components in NUXT you firstly need to add create a plugin file called plugins/iamkey.js and add the below code.
-
-```
-import Vue from 'vue'
-
-import '@iamproperty/components/assets/css/core.min.css'
-import '@iamproperty/components/dist/components.css'
-
-import * as iamkey from '@iamproperty/components'
-for (const [key, value] of Object.entries(iamkey)) {
-  Vue.component(key, value)
-}
-```
-
-Then add the plugin to the nuxt.config.js file.
-
-```
-export default {
-  plugins: [
-    'plugins/iamkey.js'
-  ],
-}
-```
-
-
-## Contributing to iam key
-
-### Create code branch
-
-Firstly the clone the [repo](https://github.com/iamproperty/iamproperty-vue-component-library) from GitHub and create a new branch using the agreed naming conventention. 
-
-### Commands
-
-#### Install node packages
-
-```
-npm install
-```
-
-#### Development local web server
-
-Setup a local web server to run the documentation site this will allow you to modify the code and check it.
-
-```
-npm run serve
-```
-
-#### Run your unit tests
-
-**This command should be ran while the local web server is still running.**
-
-Unit tests should be ran after changing any code to make sure it has no unwanted side effects.
-
-The visual regression tests may differ greatly if the tests are running on a windows when the the snapshots where created on Mac.
-
-```
-npm run test
-```
-
-#### Prepare for pull request
-
-**This command should be ran while the local web server is still running.**
-
-Before creating a pull request we want to make sure assets get re-compiled and audited so that we can keep an eye on file sizes. We also want to recreate visual regression snapshots. This will create a number of files that will be added to the pull request to help the reviewers make judgement on the changes.
-
-```
-npm run pull-request
-```
-
-### Pull request
-
-You will not have the ability to commit changes directly to the main branch and a pull request will have to be created. This pull request should follow the format dictated in the .github/pull_request_template.md file.
-
-## Create release
-
-Before creating a release you will need to make sure you are logged into the npm registry by running the below command. You will also need to make sure you have access to create releases to the <a href="https://www.npmjs.com/package/@iamproperty/components" target="_blank">npm registry package</a>.
-
-```
-npm login
-```
-
-After you are logged in then can publish but remember to increase the package version if the package.json file.
-
-```
-npm publish
-```
+You can learn more about Take Over mode [here](https://github.com/johnsoncodehk/volar/discussions/471).