solumy / engine Goto Github PK

Goal

Today, we can't customise a card with a background color, shadow, radius, margin or padding

It would be better to have this properties customizables in a cartd component

In order to achieve that, we could create a card component with background color, shadow, radius, margin or padding properties

How to

In order to solve this issue, you are invited to fork this GitHub repository, makes changes to it, and then create a Pull Request so we can merge your changes back to this repository.

First, you may want to read about:

• How to propose a valuable contribution to this repo: CONTRIBUTING.md

I will be happy to assist you at any stage, if you want to try to solve this issue! If you have any question, just leave a comment below. Beginners are also welcome! 🤗

Goal

Today, we can't create an image with a custom width, height, alt and border

It would be better to have an image component with a width, height, alt and border properties with default values to customise the display. Also the src of the image could be a path of an image in a public directory or a url

In order to achieve that, we could create an image component with path, width, height, alt and border properties

How to

In order to solve this issue, you are invited to fork this GitHub repository, makes changes to it, and then create a Pull Request so we can merge your changes back to this repository.

First, you may want to read about:

• How to propose a valuable contribution to this repo: CONTRIBUTING.md

I will be happy to assist you at any stage, if you want to try to solve this issue! If you have any question, just leave a comment below. Beginners are also welcome! 🤗

Goal

Today, I can't organise my components through a container for a landing page

It would be better to have a container where we can setup the width for all the content (and so the page) or a default value to 1140 for example

In order to achieve that, we could create a container component with a max-width property

How to

In order to solve this issue, you are invited to fork this GitHub repository, makes changes to it, and then create a Pull Request so we can merge your changes back to this repository.

First, you may want to read about:

• How to propose a valuable contribution to this repo: CONTRIBUTING.md

I will be happy to assist you at any stage, if you want to try to solve this issue! If you have any question, just leave a comment below. Beginners are also welcome! 🤗

Goal

Today, we can't design a link as a button

It would be better to have a display property for a link so we can set it to "primary-button" / "secondary-button"

In order to achieve that, we could add a property "display" for a link that reuse the UI of the button component

How to

In order to solve this issue, you are invited to fork this GitHub repository, makes changes to it, and then create a Pull Request so we can merge your changes back to this repository.

First, you may want to read about:

• How to propose a valuable contribution to this repo: CONTRIBUTING.md

I will be happy to assist you at any stage, if you want to try to solve this issue! If you have any question, just leave a comment below. Beginners are also welcome! 🤗

Goal

Today, I can't organise my components by rows

It would be better to have a rows component that organise components in rows with default and custom margin and padding between them

In order to achieve that, we could create a "rows" component with margin and padding properties

How to

In order to solve this issue, you are invited to fork this GitHub repository, makes changes to it, and then create a Pull Request so we can merge your changes back to this repository.

First, you may want to read about:

• How to propose a valuable contribution to this repo: CONTRIBUTING.md

I will be happy to assist you at any stage, if you want to try to solve this issue! If you have any question, just leave a comment below. Beginners are also welcome! 🤗

Goal

Today, we can sho or hide a component when we toggle a button

It would be better to have a property in component that conditionally show it depending of the page state

In order to achieve that, we could add a displayCondition property for all components with a formula

How to

In order to solve this issue, you are invited to fork this GitHub repository, makes changes to it, and then create a Pull Request so we can merge your changes back to this repository.

First, you may want to read about:

• How to propose a valuable contribution to this repo: CONTRIBUTING.md

I will be happy to assist you at any stage, if you want to try to solve this issue! If you have any question, just leave a comment below. Beginners are also welcome! 🤗

Goal

Today, every page are public

It would be better to have a property to secure access to pages for logged user

In order to achieve that, we could specified which pages for each roles are privates and let Solumy Systems allowed the access or not

How to

In order to solve this issue, you are invited to fork this GitHub repository, makes changes to it, and then create a Pull Request so we can merge your changes back to this repository.

First, you may want to read about:

• How to propose a valuable contribution to this repo: CONTRIBUTING.md

I will be happy to assist you at any stage, if you want to try to solve this issue! If you have any question, just leave a comment below. Beginners are also welcome! 🤗

Goal

Today, we can't use a toggle component to update page values

It would be better to have a toggle component with a name and a value for both option that update a state shared between all the page with static values, like for a pricing page where prices change when we toggle the subscription scope

In order to achieve that, we could create a toggle component and add a state value to the context that contain key / value pairs. This component can be composed of texts or icons with 2 displays : replace (the one or the other is displayed) or switch (both displayed but with a color for the selected one)

How to

In order to solve this issue, you are invited to fork this GitHub repository, makes changes to it, and then create a Pull Request so we can merge your changes back to this repository.

First, you may want to read about:

• How to propose a valuable contribution to this repo: CONTRIBUTING.md

I will be happy to assist you at any stage, if you want to try to solve this issue! If you have any question, just leave a comment below. Beginners are also welcome! 🤗

Goal

Today, we can't organise components by columns

It would be better to have a columns components with a sizes property for all components, which allowed us to determine what is the size of each column (fixed, basis, full, etc...) and a align property for all components

In order to achieve that, we could create a "columns" component with a sizes property which is an array of sizes for each columns / components and their position between the top, the middle and the bottom of the column

How to

In order to solve this issue, you are invited to fork this GitHub repository, makes changes to it, and then create a Pull Request so we can merge your changes back to this repository.

First, you may want to read about:

• How to propose a valuable contribution to this repo: CONTRIBUTING.md

I will be happy to assist you at any stage, if you want to try to solve this issue! If you have any question, just leave a comment below. Beginners are also welcome! 🤗

Goal

Today, we can't customise each component design as we want

It would be better to have the option to set classnames or/and styles in each element of a component from a config

In order to achieve that, we could add an elements property in components that represent the elements tree where we can set html attributes like classe or style

How to

In order to solve this issue, you are invited to fork this GitHub repository, makes changes to it, and then create a Pull Request so we can merge your changes back to this repository.

First, you may want to read about:

• How to propose a valuable contribution to this repo: CONTRIBUTING.md

I will be happy to assist you at any stage, if you want to try to solve this issue! If you have any question, just leave a comment below. Beginners are also welcome! 🤗

Goal

Today, we can't login a new user in the app

It would be better to have an action property on the button component in order to sign in

In order to achieve that, we could add an action property to the button component and setup sign-in as an action

How to

In order to solve this issue, you are invited to fork this GitHub repository, makes changes to it, and then create a Pull Request so we can merge your changes back to this repository.

First, you may want to read about:

• How to propose a valuable contribution to this repo: CONTRIBUTING.md

I will be happy to assist you at any stage, if you want to try to solve this issue! If you have any question, just leave a comment below. Beginners are also welcome! 🤗

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'node index.mjs'
2. See error:
   throw new Error(Schema ${schema} not found in ${schemaPath});

My code
import App from '@solumy/engine'

(async () => {
const app = new App()
const url = await app.start({
name: 'Hello world website',
features: [
{
name: 'website',
pages: [
{
name: 'home',
path: '/',
body: [
{
component: 'Title',
text: 'Hello world!',
},
],
},
],
},
],
})

console.log(Server started at ${url})
})();

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Windows 10
• Browser EDGE
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Goal

Today, we can't use icons as components

It would be better to have an icon component where we can name the icon we want to display his size

In order to achieve that, we could create an icon component with name and size

How to

In order to solve this issue, you are invited to fork this GitHub repository, makes changes to it, and then create a Pull Request so we can merge your changes back to this repository.

First, you may want to read about:

• How to propose a valuable contribution to this repo: CONTRIBUTING.md

I will be happy to assist you at any stage, if you want to try to solve this issue! If you have any question, just leave a comment below. Beginners are also welcome! 🤗

Goal

Today, we have to use the columns feature to add an icon before a paragraph

It would be better to have an icon property for a paragraph where we can set the name to display it

In order to achieve that, we could add an icon property to the paragraph component that load the corresponding icon if set

How to

In order to solve this issue, you are invited to fork this GitHub repository, makes changes to it, and then create a Pull Request so we can merge your changes back to this repository.

First, you may want to read about:

• How to propose a valuable contribution to this repo: CONTRIBUTING.md

I will be happy to assist you at any stage, if you want to try to solve this issue! If you have any question, just leave a comment below. Beginners are also welcome! 🤗

Goal

Today, we can't register a new user in the app

It would be better to have an action property on the button component in order to sign up

In order to achieve that, we could add an action property to the button component and setup sign-up as an action

How to

In order to solve this issue, you are invited to fork this GitHub repository, makes changes to it, and then create a Pull Request so we can merge your changes back to this repository.

First, you may want to read about:

• How to propose a valuable contribution to this repo: CONTRIBUTING.md

I will be happy to assist you at any stage, if you want to try to solve this issue! If you have any question, just leave a comment below. Beginners are also welcome! 🤗