Giter Club home page Giter Club logo

askui's Introduction

askui logo askui logo

Reliable, automated end-to-end-automation that only depends on what is shown on your screen instead of the technology or platform you are running on


What Can Be Said Can Be Solved

Disclaimer

This repo contains the AskUI SDK (ADK) written in TypeScript. Releases are done from the root repository. This may change in the future as we plan to include also packages, libraries etc. written in other languages in this repo to make the power of AskUI available to non-typescript/-javascript developers as well.

Repository Structure

At root level we store the configuration for commit hooks, CI/CD and releasing a new version of the ADK.

Under packages you find the ADKs for different languages.

Installation

Run an npm install inside the root directory to install the necessary dependencies for commit hooks and releasing a new version.

$ npm install

TypeScript ADK

Run npm install inside packages/askui-nodejs to install the dependencies.

To build the TypeScript ADK run

npm run build

Contributing

Branching

Your branch name should conform to the format <issue id>-<issue title lower-cased and kebab-cased>, e.g., let's say you have an issue named Hello World with id AS-101, the the branch name would be AS-101-hello-world. We use the issue id prefix to prepend a link to the issue to the commit message header. In some cases, when doing a quick fix of a typo etc. when there is no issue, feel free to just use a descriptive name of what you are doing, e.g., fix-typo-in-example-readme.

Commit Message Standard

Commit messages should conform to Conventional Commits Message Standard. Exceptions to this rule may be merge commits.

Githooks

This monorepo uses githooks with husky to lint and test the code, to help you stick to the commit message standard by opening up a cli for constructing the commit message on each commit, prepending the commit message with the issue number or linting the commit message etc. In some cases, e.g., when using a Git client such as Git Tower or GitKraken, cherry-picking, rebasing or in a ci pipeline, you may want to disable githooks, especially the interactive cli.

For skipping the interactive cli when commiting, set the environment variable SKIP_CZ_CLI to true.

$ export SKIP_CZ_CLI=true

For skipping all githooks, set the environment variable HUSKY to 0.

$ export HUSKY=0

In a ci pipeline, the githooks are skipped by default.

askui's People

Contributors

adi-wan-askui avatar choiharam avatar dependabot[bot] avatar gauravkhuraana avatar gitlost-murali-askui avatar haramchoi-askui avatar james-bot-askui avatar johannesdienst-askui avatar lumpin-askui avatar maxi-askui avatar mlikasam-askui avatar mrmeier-1 avatar premith-askui avatar programminx-askui avatar programmnix avatar thinh-askui avatar

Stargazers

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

Watchers

 avatar  avatar  avatar  avatar

askui's Issues

scrollUntil# ScrollUntil

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

scrollUntil

ScrollUntil

Problem

Whenever the current user wants to scroll to find an elements,they are forced to guess the scroll offset

Solution:

A scrollUntil function, so that the user will only write ,until which element they want to scroll and not care about the scroll offset

Notes:

please Make sure to do it as fast as possible, I want the user to enjoy using ME as testing solution
** Feature Request, that was requested by the askui Nodejs package ๐Ÿ‘‘ **

scrollUntil

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

scrollUntil# ScrollUntil

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

[NEVER MIND / RESOLVED / OOPS!] "npx askui init" results in Error: Cannot find module '../dist/cjs/lib/copy-example-project'

** Never Mind **

I had neglected to "npm init -y" and that solved it.

Describe the bug

Having followed your tutorial steps at https://docs.askui.com/docs/general/Getting%20Started/getting-started ,
when I run "npm askui init" on my node installation (node 16.14.2 on Ubuntu 20.04 in WSL2), I get the following error:

npx askui init
node:internal/modules/cjs/loader:936
throw err;
^

Error: Cannot find module '../dist/cjs/lib/copy-example-project'
Require stack:

  • /home/liam/src/askui-test/askui/packages/askui-nodejs/bin/askui
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
    at Function.Module._load (node:internal/modules/cjs/loader:778:27)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object. (/home/liam/src/askui-test/askui/packages/askui-nodejs/bin/askui:3:1)
    at Module._compile (node:internal/modules/cjs/loader:1103:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1157:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12) {
    code: 'MODULE_NOT_FOUND',
    requireStack: [ '/home/liam/src/askui-test/askui/packages/askui-nodejs/bin/askui' ]
    }

To Reproduce
Steps to reproduce the behavior:

  1. Follow steps at https://docs.askui.com/docs/general/Getting%20Started/getting-started
  2. npx askui init

Expected behavior
I expected the tutorial's next command to succeed.

Desktop (please complete the following information):

  • OS: Ubuntu 20.04 on WSL2
  • Browser: N/A (not used yet, but was planning to use google-chrome)
  • Version N/A (was planning to use google-chrome 103.0.5060.114)

node --version
v16.14.2
npm --version
8.13.2

Additional context
Thanks for your patience if this is a stupid question. I'm not an experienced Node developer. I get the impression I may need to install and configure grunt and a gruntfile, in order for the "dist" directory to exist? Can you give me any more specific guidance?

Better yet, could you produce a Dockerfile that sets up all dependencies? Could be a way to ensure you haven't omitted any of them from the tutorial.

I think the error is generated from one of the following lines:

./node_modules/.bin/askui:require('../dist/cjs/lib/copy-example-project').init();
./packages/askui-nodejs/bin/askui:require('../dist/cjs/lib/copy-example-project').init();

Thank you!

controlui-server: Excessive log noise; suspect packaging issue

Describe the bug
On macOS, syslogs are filled with many useless messages indicating a missing Folder PlugIns in ... node_modules/askui/dist/release/latest/darwin/controlui-server.app/Contents/PlugIns.

This looks like an issue with the packaging of the app.

To Reproduce

  • Start Console.app, filter for controlui-server
  • Launch contolui-server.app
  • Feel slightly overload by same log message 100s of times.

Expected behavior
Only useful log messages.

Desktop (please complete the following information):
macOS 12.4 on M1

scrollUntil

ScrollUntil

Problem

Whenever the current user wants to scroll to find an elements,they are forced to guess the scroll offset

Solution:

A scrollUntil function, so that the user will only write ,until which element they want to scroll and not care about the scroll offset

Notes:

please Make sure to do it as fast as possible, I want the user to enjoy using ME as testing solution
** Feature Request, that was requested by the askui Nodejs package ๐Ÿ‘‘ **

scrollUntil# ScrollUntil

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

scrollUntil# ScrollUntil

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

scrollUntil

ScrollUntil

Problem

Whenever the current user wants to scroll to find an elements,they are forced to guess the scroll offset

Solution:

A scrollUntil function, so that the user will only write ,until which element they want to scroll and not care about the scroll offset

Notes:

please Make sure to do it as fast as possible, I want the user to enjoy using ME as testing solution
** Feature Request, that was requested by the askui Nodejs package ๐Ÿ‘‘ **

scrollUntil# ScrollUntil

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

scrollUntil# ScrollUntil

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

scrollUntil# ScrollUntil

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

scrollUntil# ScrollUntil

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

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.