Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PHI/UNPHI Removes All unlint And version Metas #3812

Closed
volodya-lombrozo opened this issue Jan 14, 2025 · 6 comments · Fixed by #3816
Closed

PHI/UNPHI Removes All unlint And version Metas #3812

volodya-lombrozo opened this issue Jan 14, 2025 · 6 comments · Fixed by #3816

Comments

@volodya-lombrozo
Copy link
Member

volodya-lombrozo commented Jan 14, 2025

I have XMIR file with the following metas:

<metas>
    <meta>
        <head>package</head>
        <tail>j$org.j$eolang.j$hone</tail>
        <part>j$org.j$eolang.j$hone</part>
    </meta>
    <meta>
        <head>unlint</head>
        <tail>mandatory-package</tail>
    </meta>
    <meta>
        <head>version</head>
        <tail>0.1.0-SNAPSHOT</tail>
    </meta>
</metas>

Then I do the following:

  1. Convert this XMIR into PHI (phi)
  2. Convert PHI back to XMIR (unphi)
  3. Unroll PHI modifications (unroll from jeo-maven-version)

After all of there thransformations I get the XMIR without unlint and version metas:

<metas>
    <meta line="1">
        <head>package</head>
        <tail>j$org.j$eolang.j$hone</tail>
        <part>j$org.j$eolang.j$hone</part>
    </meta>
</metas>

This causes some errors in following pipelines. Please, keep all the metas in phi/unphi transformations up to the end.

@volodya-lombrozo
Copy link
Member Author

volodya-lombrozo commented Jan 14, 2025

@volodya-lombrozo
Copy link
Member Author

Blocks objectionary/jeo-maven-plugin#962

@volodya-lombrozo
Copy link
Member Author

@maxonfjvipon Could you have a look, please?

@maxonfjvipon
Copy link
Member

@volodya-lombrozo I think it's impossible since PHI notation does not support metas

@maxonfjvipon
Copy link
Member

@yegor256 any ideas?

@yegor256
Copy link
Member

yegor256 commented Jan 14, 2025

@volodya-lombrozo indeed, there is no simple way to do this (and I'm sure we have to, since this information is EO-related, not model related). Maybe you can inject +unlint and +version into the XMIR when you get it back from phi-to-xmir mojo? Otherwise, just skip the linting step in production, it's a redundancy, I believe.

volodya-lombrozo added a commit to volodya-lombrozo/eo that referenced this issue Jan 15, 2025
volodya-lombrozo added a commit to volodya-lombrozo/eo that referenced this issue Jan 15, 2025
yegor256 added a commit that referenced this issue Jan 15, 2025
 feat(#3812): Extend Docs About 'PHI/UNPHI' Issues
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants