objectionary / objectionary/lints

unknown-metas reports the new 'also' meta as unknown

Open Beginner friendly
#1,380 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Java
Stars
14
Forks
39
Avg merge
22h 54m
Merged PRs (30d)
90

Description

Problem

unknown-metas reports +also as an unknown meta, although the modern parser emits it (see add-default-package.xsl in eo-parser).

Root cause

src/main/resources/org/eolang/lints/metas/unknown-metas.xsl:15 whitelists a fixed set of meta heads (package, architect, version, home, spdx, rt, lint, tests, unlint, import, alias, compile, repo, register, system, ...) — also is not among them, so any +also ... is flagged as unknown.

Minimal example

+package x
+architect yegor@256.com
+version 0.0.1
+home https://github.com/objectionary
+spdx SPDX-FileCopyrightText: Copyright (c) 2026 Objectionary.com
+spdx SPDX-License-Identifier: MIT
+also app

[] > main

+also app is reported as an unknown meta.

Expected behavior

also should be added to the list of known metas (and kept in sync with the metas the parser can emit).

Related

  • eo-parser add-default-package.xsl (introduces +also).
  • Existing packs under packs/single/unknown-metas/.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with src/main/resources/org/eolang/lints/metas/unknown-metas.xsl:15 and compare its known-meta list with the +also output described from eo-parser's add-default-package.xsl. Review the existing packs under packs/single/unknown-metas/ and add coverage for the minimal example. Done means +also is accepted without an unknown-meta report while existing unknown metas remain flagged.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Bug
Difficulty
1/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
88/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.