Coder Social home page Coder Social logo

lutris-dashboard's Introduction

vue-admin-box

vue element-plus vite typescript license

简介

  • 更新日志
  • 经过三个多月的迭代,于2021年8月10日,1.0版本正式发布,并附四个基础模板供大家使用
  • 此开源项目为个人开发,不限制任何商业使用和个人研究,使用之前请先点个Star对我进行鼓励
  • 利用此开源项目参与的一切违法、色情相关的活动均与本源码无关,请勿以身示法

预览

基础模板

共四个基础模板,均适合从零研发使用,可在vue-admin-box-template仓库中直接查看,模板如下所示

  1. template-ts-i18n 基础模板,内含ts语法+国际化配置 demo
  2. template-ts 基础模板,只含ts语法,国际化已去除 demo
  3. template-js-i18n 基础模板,js语法 + 国际化配置 demo
  4. template-js 基础模板,js语法,国际化已去除 demo

介绍

vue-admin-box是一个免费并且开源的中后台管理系统模板。使用最新版本的vue3+vite+element-plus开发而成,目的是为了解决通用型的业务中后台系统复杂的配置。

特色功能

  • 适合中后台开发的路由配置、状态管理机制(状态默认支持本地存储)、已封装完善的axios及api管理机制
  • 极方便扩展的主题配置功能,默认支持三种典型的中后台风格
  • 简易配置的页面缓存功能,只需配置noCache属性,无需配置其他的任何属性,如组件名称,路由名称等等很多框架需要配置的东西
  • 典型增删改查的三种业务表格,详情请查看“页面栏目”内的“业务表格”、“分类联动表格”、“树联动表格”
  • 无路由跳转的刷新功能,支持缓存页面刷新,目前了解的多数框架都不支持缓存页面的刷新
  • 方便扩展的国际化解决方案,并提供了两套非国际化的基础模板和两套国际化的基础模板(ts版本/js版本)
  • 手写版本的各类自定义指令
  • 已经过多个中后台业务检验过的表格公用组件及弹窗公用组件,详情请查看“页面栏目”内的“业务表格”、“分类联动表格”、“树联动表格”

主要技术栈

  • MVVM框架:vue v3
  • 工程化管理:vite v2
  • UI框架:element-plus
  • 路由管理:vue-router v4
  • 状态管理:vuex v4
  • 数据请求:axios
  • 实用工具库:@vueuse/core

效果预览

使用

  1. 获取源码资源包

    git clone https://github.com/cmdparkour/vue-admin-box.git
    
  2. 安装依赖,国内推荐使用cnpm或tyarn,国外推荐使用npm或yarn

    npm install
    
  3. 运行

    npm run dev 或 npm run start
    
  4. 打包

    npm run build
    

lutris-dashboard's People

Contributors

dependabot[bot] avatar prettydiff avatar smichel17 avatar strycore avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

lutris-dashboard's Issues

Allow to edit installers that are under review

Very often the installers that we review can be alright but may contain a tiny mistake or an awful name, which can be easily fixed. But currently, there's no way to do that from the dashboard, you have to look for the game on the website yourself and edit the installer manually which after a few of them makes you go insane.

Don't exit when accepting/removing submissions/drafts if there are still some available

Once a submission/draft is accepted/deleted the page exits back to the submissions page. Instead, it should load another draft/submission if there are any available.

With the way it is now you have to review the installer, accept/delete installer, go back to game page, reload to refresh review button, and review the remaining edits. Repeat that process until there aren't any left.

It's tedious.

Merge installers

This happens a lot:

  1. Installer version X doesn't work
  2. Someone forks installer X and submits it as version X (fixed)

Current workaround:

  • Accept and publish installer X (fixed)
  • Delete installer X
  • Rename X (fixed) back to X

This is extra work and means that the history for installer X is lost.

It would be better if I could instead accept the X (fixed) version and then merge it into X. The merging implementation would take these actions:

  • Adds the most recent revision of X (fixed) as a revision of X.
  • Deletes X (fixed)

Sort new installer submissions by submission date

Currently, installer updates are sorted by submission date (most recent first, to form a LIFO queue). However, new installers are sorted alphabetically. Most of the current first page of submissions has something that makes them hard to approve for one reason or another (and I do not want to reject them; see #26), so this view is basically useless at the moment :(

Add an action between Accept and Reject

While some installers should be rejected outright (piracy, shady sources, etc), more often I want to follow up with the submitter and and questions or request changes.

For example, recently someone submitted an installer for GOG's Windows version of Another World. There is already an installer for GOG's native version, so our policy is not to accept the Windows version in that scenario… unless it has features that the native one lacks. So in this case, rather than reject outright, I'd like to ask the submitter why they wanted the Windows version when the native one already exists. Otherwise I have to choose between accepting an unnecessary installer, rejecting a useful installer, or doing the work of researching why the Windows installer may be needed (In this case I chose to do nothing, and someone else accepted the installer later, so the submission is no longer available).

It would be nice to have a third option, something like "Reject with reason" or "Request information/changes", that allows moderators to send a message to submitters and preserves the installer. The message could be sent through email or appear on the submitter's dashboard; the submission could either be included in the message or set back to draft status.

Add pagination

I would like to be able to see how many pages of unmoderated installers I have to deal with and browse through them.

After validated a submitted script, you have to reject all older submitted script versions

Hello,
when I validate a submitted script modification, I have to reject all older submitted script modifications.
Sometimes there are more than 20 modifications to reject, it takes a lot of time and it is useless as we have already validated a script.
What about to automatically reject all all older submitted script versions when a modo validated one of them?

List of duplicates

Field for editing the script is too small

When reviewing an installer, if you first edit the "notes" field or any other field but "script", and then edit the "script" field, the "script' field will be very small. This hinders the reviewing process.
Observe:
Peek 2021-12-10 04-31

Sorting preference is not remembered

If I switch sorting preference to "oldest", this sorting rule will reset if I review an installer, close the page or switch to another tab (like new installers). This requires pressing the button after each review which is very inconvenient.

Dashboard: diffs are broken for some installers

Diffs are kinda fucked

The installer: line is not actually there in the submission at the bottom, but it's shown like it's added there
image

Add Oldest/Newest sorting

I would to be able to view installers that were the oldest to be submitted instead of newest, and be able to choose between 2 options.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.