oscript-library / oscript-library/opm
Формат описания packagedef
Open
Nobody has claimed this yet.
wontfix
- Dominant language
- 1C Enterprise
- Stars
- 85
- Forks
- 35
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Как разработчик хочу иметь возможность указывать настройки пакета в формате yaml
Пример файла ниже
name: YAML
version: 0.0.1
description: Конвертация и чтение в формат YAML
executable:
class: 'yaml2.os'
engine-version: '*'
include-content:
- 'src/*'
- 'tests/*'
- 'bin/*'
- readme.md
explicit-modules:
- '*'
keywords:
- null
repository:
type: git
url: ..
author:
name: Автор
email: Почта
url: url
depends-on:
logos: 1.1.0
cmdline: ^3.0.6
tempfiles: '^3.4.3"'
tool1cd: ^2.0.0
v8runner: ^4.0.0
strings: '*'
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue provides a YAML packagedef example but names no files, tests, or entry points. Start by locating how package descriptors are currently read, then determine the required behavior for accepting the shown YAML structure and add coverage for that format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- yaml
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100