Compare revisions

# apiDocs

# Coscine ApiDocs

This template should help get you started developing with Vue 3 in Vite.

[[_TOC_]] 

## Recommended IDE Setup

## 📝 Overview

[VSCode](https://code.visualstudio.com/) + [Volar](https://marketplace.visualstudio.com/items?itemName=Vue.volar) (and disable Vetur) + [TypeScript Vue Plugin (Volar)](https://marketplace.visualstudio.com/items?itemName=Vue.vscode-typescript-vue-plugin).

This project renders Coscine's API Docs with the help of [Scalar](https://github.com/scalar/scalar)!

## Type Support for `.vue` Imports in TS

## ⚙️ Configuration

TypeScript cannot handle type information for `.vue` imports by default, so we replace the `tsc` CLI with `vue-tsc` for type checking. In editors, we need [TypeScript Vue Plugin (Volar)](https://marketplace.visualstudio.com/items?itemName=Vue.vscode-typescript-vue-plugin) to make the TypeScript language service aware of `.vue` types.

[![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://git.rwth-aachen.de/coscine/frontend/apps/apidocs)

If the standalone TypeScript plugin doesn't feel fast enough to you, Volar has also implemented a [Take Over Mode](https://github.com/johnsoncodehk/volar/discussions/471#discussioncomment-1361669) that is more performant. You can enable it by the following steps:

(For a specific branch, build such a URL: `https://gitpod.io/#https://git.rwth-aachen.de/coscine/frontend/apps/apidocs/tree/{branch}`)

1. Disable the built-in TypeScript Extension

    1) Run `Extensions: Show Built-in Extensions` from VSCode's command palette

    2) Find `TypeScript and JavaScript Language Features`, right click and select `Disable (Workspace)`

2. Reload the VSCode window by running `Developer: Reload Window` from the command palette.

## 📖 Usage

## Customize configuration

This project uses [Yarn](https://yarnpkg.com/) and [Node.js](https://nodejs.org/en/) to manage its dependencies.

See [Vite Configuration Reference](https://vitejs.dev/config/).

## Project Setup

```

yarn install

```

```sh

npm install

### Compiles and hot-reloads for development

```

yarn dev

```

### Compile and Hot-Reload for Development

### Compiles and minifies for production

```

yarn build

```

```sh

npm run dev

### Runs the minified production build

```

yarn preview

```

### Type-Check, Compile and Minify for Production

### Lints files

```

yarn lint

```

```sh

npm run build

### Lints and fixes files

```

yarn lint:fix

```

### Lint with [ESLint](https://eslint.org/)

## 👥 Contributing

```sh

npm run lint

```

As an open source plattform and project, we welcome contributions from our community in any form. You can do so by submitting bug reports or feature requests, or by directly contributing to Coscine's source code. To submit your contribution please follow our [Contributing Guideline](https://git.rwth-aachen.de/coscine/docs/public/wiki/-/blob/master/Contributing%20To%20Coscine.md).

## 📄 License

The current open source repository is licensed under the **MIT License**, which is a permissive license that allows the software to be used, modified, and distributed for both commercial and non-commercial purposes, with limited restrictions (see `LICENSE` file)

> The MIT License allows for free use, modification, and distribution of the software and its associated documentation, subject to certain conditions. The license requires that the copyright notice and permission notice be included in all copies or substantial portions of the software. The software is provided "as is" without any warranties, and the authors or copyright holders cannot be held liable for any damages or other liability arising from its use.

## 🆘 Support

1. **Check the documentation**: Before reaching out for support, check the help pages provided by the team at https://docs.coscine.de/en/. This may have the information you need to solve the issue.

2. **Contact the team**: If the documentation does not help you or if you have a specific question, you can reach out to our support team at `servicedesk@itc.rwth-aachen.de` 📧. Provide a detailed description of the issue you're facing, including any error messages or screenshots if applicable.

3. **Be patient**: Our team will do their best to provide you with the support you need, but keep in mind that they may have a lot of requests to handle. Be patient and wait for their response.

4. **Provide feedback**: If the support provided by our support team helps you solve the issue, let us know! This will help us improve our documentation and support processes for future users.

By following these simple steps, you can get the support you need to use Coscine's services as an external user.

## 📦 Release & Changelog

External users can find the _Releases and Changelog_ inside each project's repository. The repository contains a section for Releases (`Deployments > Releases`), where users can find the latest release changelog and source. Withing the Changelog you can find a list of all the changes made in that particular release and version.  

By regularly checking for new releases and changes in the Changelog, you can stay up-to-date with the latest improvements and bug fixes by our team and community!

{

  "name": "apidocs",

  "version": "1.0.1",

  "version": "1.0.2",

  "private": true,

  "scripts": {

    "dev": "vite",

<template>

  <ApiReference

    :configuration="{

      spec: { url: 'https://' + getHostName() + '/coscine/api/swagger/v2/swagger.json' }

      // Workaround from https://github.com/scalar/scalar/issues/440

      proxy: 'https://api.scalar.com/request-proxy',

      spec: {

        url: 'https://' + getHostName() + '/coscine/api/swagger/v2/swagger.json' 

      }

    }"

  >

    <template #footer>